Apparatuses, methods, and computer program products for centralized channel management in a group-based communication system

ABSTRACT

Centralized channel management of a set group-based communication system is described. A channel management interface, of the group-based communication system, can be presented via a client of a user associated with a first organization, wherein the channel management interface includes communication channels associated with the first organization, wherein at least a first communication channel is associated with the first organization and a second organization, and wherein at least a second communication channel is associated with the first organization and a third organization. A request can be received via the channel management interface to initiate a channel management action associated with at least one of the first communication channel or the second communication channel and in response to receiving the request to initiate the channel management action, data associated with at least one of the first communication channel or the second communication channel can be updated.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 16/779,513, filed on Jan. 31, 2020, entitled“Apparatuses, Methods, And Computer Program Products For CentralizedChannel Management In A Group-Based Communication System”, which willissue as U.S. Pat. No. 11,089,445 on Aug. 10, 2021, and is fullyincorporated by reference herein.

TECHNOLOGICAL FIELD

Embodiments of the present disclosure generally relate to applicationprogramming interface functionality and interfaces for data objectconfiguration, and specifically to improved functionality and interfacesfor management of any number of group-based communication channels in agroup-based communication system.

BACKGROUND

In a group-based environment, channels provide unique data objectsstructured to enable separation of users, conversations, topics, and/orthe like. However, as a group-based environment begins to grow incomplexity, for example over time as an increasing number of channels,workspaces, or other data objects are created and/or otherwisemaintained, the task of efficiently managing the channels also increasesin complexity. As the number of channels and/or complexity of channelmanagement configurations increases, individual management of eachchannel can become impractical or inefficient. Various accounts may beconfigured to access channels with various permissions (e.g., asmembers, guest members, or the like), and if permissions for accountaccess are left unchecked, data security and/or data privacyvulnerabilities, and/or other data management vulnerabilities, maybecome present as permissions for various user accounts are not properlymaintained. Such risks are exacerbated in circumstances where sufficientprocedural tools (e.g., application program interfaces or “APIs”) and/orcorresponding user interfaces are not provided for management of channeldata and/or permissions, and/or for configuring permissions formanagement of channels by one or more user accounts. Further, withoutsufficient data attribution with respect to channel managementpermissions, data exposure with respect to one or more channels may beconfusing to any number of users or may increase the likelihood ofviolations of data privacy legislation, policies, and/or businessobligations/promises. Applicant has discovered problems with currentimplementations, such as systems, methods, apparatuses, and computerprogram products, for channel management in a group-based environment,for example via a group-based communication system, and through appliedeffort, ingenuity, and innovation, Applicant has solved many of theseidentified problems by developing embodied in the present disclosure,which are described in detail below.

BRIEF SUMMARY

In general, embodiments of the present disclosure provided hereininclude systems, methods, apparatuses and computer program products forcentralized channel management via a group-based communication system.Other systems, apparatuses, methods, computer readable media, andfeatures will be, or will become, apparent to one with skill in the artupon examination of the following figures and detailed description. Itis intended that all such additional systems, apparatuses, methods,computer readable media, and features be included within thisdescription be within the scope of the disclosure, and be protected bythe following claims.

In accordance with at least one aspect of the present disclosure, acomputer-implemented method is provided. The computer-implemented methodmay be performed using any of a myriad of implementations embodied inhardware, software, firmware, and/or a combination thereof, as describedherein. In at least one example, the computer-implemented methodincludes receiving centralized channel data including a group-basedcommunication channel metadata set for each group-based communicationchannel in a manageable group-based communication channel set for anauthenticated user account. The computer-implemented method furtherincludes in response to receiving the centralized channel data, causingrendering of a centralized channel management dashboard based at leaston the centralized channel data, the centralized channel managementdashboard comprising the group-based communication channel metadata setfor each group-based communication channel in the manageable group-basedcommunication channel set, where the centralized channel managementdashboard further comprises at least one channel management actioninterface element associated with at least one group-based communicationchannel in the manageable group-based communication channel set.

In some embodiments of the example computer-implemented method, theauthenticated user account is associated with workspace managementpermission data linked to a workspace identifier, and the manageablegroup-based communication channel set comprises at least one group-basedcommunication channel associated with the workspace identifier.Additionally or alternatively, in some embodiments of the examplecomputer-implemented method, the authenticated user account isassociated with organization management permission data linked to anorganization identifier, and the manageable group-based communicationchannel set comprises at least one group-based communication channelassociated with the organization identifier.

In some embodiments of the example computer-implemented method, thecomputer-implemented method further includes transmitting a centralizedchannel management request to a group-based communication system, thecentralized channel management request associated with an authenticateduser account identifier corresponding to the authenticated user account.

In some embodiments of the example computer-implemented method, thecomputer-implemented method further includes transmitting, to thegroup-based communication system, channel management data associatedwith a selected group-based communication channel of the manageablegroup-based communication channel set in response to user interactionwith the at least one channel management action interface element.

Additionally or alternatively, in some embodiments of the examplecomputer-implemented method, the manageable group-based communicationchannel set comprises at least a private group-based communicationchannel, and the authenticated user account is identified by channelowner data for the private group-based communication channel ordelegated management data for the private group-based communicationchannel.

Additionally or alternatively, in some embodiments of the examplecomputer-implemented method, the group-based communication channelmetadata set comprises one or more of channel private status data,channel archive status data, channel workspace data, channelorganization-sharing status data, authenticated account member data,guest account member data, channel creation timestamp data, channelcreator account data, historical activity data, channel share statusdata, or channel guest status data.

Additionally or alternatively, in some embodiments of the examplecomputer-implemented method, the at least one channel management actioninterface element is associated with one or more of a channel postingrule action, a user access action, a channel defaulting action, achannel archive action, a channel rename action, a channel share action,or a channel delete action.

Additionally or alternatively, in some embodiments of the examplecomputer-implemented method, the manageable group-based communicationchannel set comprises at least one inaccessible group-basedcommunication channel for the authenticated user account.

In accordance with yet another aspect of the present disclosure, anapparatus for centralized channel management within a group-basedcommunication system is provided. In at least one example embodiment,the apparatus includes at least one non-transitory memory and at leastone processor. The at least one non-transitory memory includescomputer-coded instructions stored thereon. The computer-codedinstructions, in execution with the at least one processor, configurethe apparatus to perform any one of the example computer-implementedmethods described above, and/or any combination thereof. In anotherexample embodiment, the apparatus includes means for performing eachstep of any one of the example computer-implemented methods describedabove, and/or any combination thereof.

In accordance with yet another aspect of the present disclosure, acomputer program product centralized channel management within agroup-based communication system is provided. The computer programproduct includes at least one non-transitory computer-readable storagemedium having computer program code stored thereon. The computer programcode is configured, in execution with at least one processor, forperforming any of the example computer-implemented methods describedabove, and/or any combination thereof.

In accordance with yet another aspect of the present disclosure, asecond computer-implemented method is provided. The secondcomputer-implemented method may be performed using any of a myriad ofimplementations embodied in hardware, software, firmware, and/or acombination thereof, as described herein. In at least one example, thesecond computer-implemented method includes receiving, from a clientdevice, a centralized channel management request, the centralizedchannel management request associated with an authenticated user accountidentifier. The second example computer-implemented method furtherincludes identifying a group-based communication channel metadata setfor each group-based communication channel in a manageable group-basedcommunication channel set permissioned for management by anauthenticated user account associated with the authenticated useraccount identifier. The second example computer-implemented methodfurther includes transmitting, to the client device, the group-basedcommunication channel metadata set to cause rendering of a centralizedchannel management dashboard based on at least the group-basedcommunication channel metadata set, the centralized channel managementdashboard comprising the group-based communication channel metadata setfor each group-based communication channel in the manageable group-basedcommunication channel set, where the centralized channel managementdashboard further comprises at least one channel management actioninterface element associated with at least one group-based communicationchannel in the manageable group-based communication channel set.

In some embodiments of the second example computer-implemented method,identifying the group-based communication channel metadata set comprisesidentifying a group-based communication channel identifier setassociated with the manageable group-based communication channel set;and querying a channel datastore based on the group-based communicationchannel identifier set to receive, in response to the query, eachgroup-based communication channel metadata set associated with eachgroup-based communication channel identifier in the group-basedcommunication channel identifier set.

In some embodiments of the second example computer-implemented method,the second computer-implemented method further includes determining theauthenticated user account identifier is associated with workspacepermission data linked to a workspace identifier, and identifying thegroup-based communication channel metadata set for each group-basedcommunication channel in the manageable group-based communicationchannel set comprises: identifying each group-based communicationchannel metadata set for at least one group-based communication channelassociated with the workspace identifier.

In some embodiments of the second example computer-implemented method,the second computer-implemented method further includes determining theauthenticated user account identifier is associated with organizationpermission data linked to an organization identifier, and identifyingthe group-based communication channel metadata set for each group-basedcommunication channel in the manageable group-based communicationchannel set comprises: identifying each group-based communicationchannel metadata set for at least one group-based communication channelassociated with the organization identifier.

In some embodiments of the second example computer-implemented method,identifying the group-based communication channel metadata set for eachgroup-based communication channel in the manageable group-basedcommunication channel set comprises: determining the authenticated useraccount identifier is associated with channel owner data or delegatedmanagement data for a private group-based communication channel, apublic group-based communication channel, or a common group-basedcommunication channel; and identifying at least a group-basedcommunication channel metadata set for the private group-basedcommunication channel.

In some embodiments of the second example computer-implemented method,the second computer-implemented method further includes receiving, froma second client device associated with a second authenticated useraccount, a selected channel information request for a selectedgroup-based communication channel of the manageable group-basedcommunication channel set; identifying, based on the group-basedcommunication channel metadata set associated with the selectedgroup-based communication channel, channel privacy access dataassociated with the selected group-based communication channel; andtransmitting, to the second client device, the channel privacy accessdata to cause rendering of channel privacy notification information,based on the channel privacy access data, associated with the selectedgroup-based communication channel.

In some embodiments of the second example computer-implemented method,the second computer-implemented method further includes the manageablegroup-based communication channel set comprises at least oneinaccessible group-based communication channel for the authenticateduser account.

In some embodiments of the second example computer-implemented method,the second computer-implemented method further includes receiving, fromthe client device, channel management data associated with a selectedgroup-based communication channel of the manageable group-basedcommunication channel set in response to user interaction with thecentralized channel management dashboard; and processing the channelmanagement data to update the selected group-based communicationchannel.

In accordance with yet another aspect of the present disclosure, asecond example apparatus for centralized channel management within agroup-based communication system is provided. In at least one exampleembodiment, the second example apparatus includes at least onenon-transitory memory and at least one processor. The at least onenon-transitory memory includes computer-coded instructions storedthereon. The computer-coded instructions, in execution with the at leastone processor, configure the second example apparatus to perform any oneof the second example computer-implemented methods described above,and/or any combination thereof. In another example embodiment, theapparatus includes means for performing each step of any one of thesecond example computer-implemented methods described above, and/or anycombination thereof.

In accordance with yet another aspect of the present disclosure, asecond example computer program product centralized channel managementwithin a group-based communication system is provided. The secondexample computer program product includes at least one non-transitorycomputer-readable storage medium having computer program code storedthereon. The computer program code is configured, in execution with atleast one processor, for performing any of the second examplecomputer-implemented methods described above, and/or any combinationthereof.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the embodiments of the disclosure in generalterms, reference now will be made to the accompanying drawings, whichare not necessarily drawn to scale, and wherein:

FIG. 1 illustrates a block diagram of a system that may be speciallyconfigured within which embodiments of the present disclosure mayoperate;

FIG. 2 illustrates a block diagram of an example apparatus that may bespecially configured in accordance with at least one example embodimentof the present disclosure;

FIG. 3 illustrates a block diagram of another example apparatus that maybe specially configured in accordance with at least one exampleembodiment of the present disclosure;

FIG. 4A illustrates an example computing environment representingaspects of a group-based communication system, in accordance with atleast one example embodiment of the present disclosure;

FIG. 4B illustrates an example computing environment representing otheraspects of a group-based communication system, in accordance with atleast one example embodiment of the present disclosure;

FIG. 5A illustrates an example user interface including variousinformation and enabling various functionality for centralized channelmanagement, in accordance with at least one example embodiment of thepresent disclosure;

FIG. 5B illustrates an example dashboard sub-interface for alteringpermission data associated with organization-level channel management inaccordance with at least some example embodiments of the presentdisclosure;

FIG. 5C illustrates an example interface for editing permission dataassociated with group-based communication channel management, inaccordance with at least some embodiments of the present disclosure;

FIG. 6A illustrates including various information and enabling variousfunctionality for centralized channel management, in accordance with atleast one example embodiment of the present disclosure;

FIG. 6B illustrates another example user interface including variousinformation and enabling various functionality for centralized channelmanagement, in accordance with at least one example embodiment of thepresent disclosure;

FIG. 7 illustrates another example user interface including variousinformation and enabling various functionality for centralized channelmanagement, in accordance with at least one example embodiment of thepresent disclosure;

FIG. 8 illustrates another example user interface including variousinformation and enabling various functionality for centralized channelmanagement, in accordance with at least one example embodiment of thepresent disclosure;

FIG. 9 illustrates a flowchart depicting example operations for anexample process for centralized channel management, in accordance withat least some example embodiments of the present disclosure;

FIG. 10 illustrates a flowchart depicting example additional operationsfor an example process for centralized channel management, specificallyto identify a group-based communication metadata set for one or moregroup-based communication channel, in accordance with at least someexample embodiments of the present disclosure;

FIG. 11 illustrates a flowchart depicting example additional operationsfor an example process for centralized channel management, specificallyto identify a group-based communication metadata set for one or moregroup-based communication channel, in accordance with at least someexample embodiments of the present disclosure;

FIG. 12 illustrates a flowchart depicting example additional operationsfor an example process for centralized channel management, specificallyto identify a group-based communication metadata set for one or moregroup-based communication channel, in accordance with at least someexample embodiments of the present disclosure;

FIG. 13 illustrates a flowchart depicting example additional operationsfor an example process for centralized channel management, specificallyto identify a group-based communication metadata set for one or moregroup-based communication channel, in accordance with at least someexample embodiments of the present disclosure;

FIG. 14 further illustrates a flowchart depicting example additionaloperations for an example process for centralized channel management,specifically to provide channel privacy access data associated with aselected group-based communication channel, in accordance with at leastsome example embodiments of the present disclosure; and

FIG. 15 illustrates a flowchart depicting various example operations forprocesses and/or sub-processes for centralized channel management, inaccordance with at least some example embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure now will be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the disclosure are shown. Indeed,embodiments of the disclosure may be embodied in many different formsand should not be construed as limited to the embodiments set forthherein, rather, these embodiments are provided so that this disclosurewill satisfy applicable legal requirements. Like numbers refer to likeelements throughout.

Overview

Entities maintained as data objects in a group-based communicationsystem may be represented in any of a myriad of manners, with variousentities being associated with one another directly and/or indirectly.For example, in at least one example context, a group-basedcommunication system may be configured to manage any number oforganizations, each organization associated with any number ofgroup-based workspaces, and each workspace further associated with anynumber of group-based communication channels. Similarly, each of theseentities may be associated with any number of authenticated useraccounts. For example, an organization may include any number ofauthenticated user accounts indicated as members of the organization.Similarly, each group-based workspace may be configured for access withany number of authenticated user accounts as members of the group-basedworkspace, such as where the authenticated user account(s) is/arepermissioned to access all or a portion of the group-based workspace.Further still, each group-based communication channel may be configuredas accessible by a desired subset of members within the associatedgroup-based workspace.

In this regard, any number of group-based communication channels may bemanaged by one or more user accounts to configure the group-basedcommunication channel for managing access permissions, data storage,and/or other settings as desired. In at least one example context,channel management may include viewing information associated withgroup-based communication channels, changing one or more settings valuesfor one or more group-based communication channels (e.g., to configurethe one or more group-based communication channels as a commongroup-based communication channel shared with one or more otherorganizations, or to remove such sharing permissions), grantingpermission data to one or more user accounts for accessing one or moregroup-based communication channels, and/or removing permission dataassociated with one or more authenticated user accounts to remove accessto one or more group-based communication channels. Various administratoruser accounts may be permissioned for managing one or more group-basedcommunication channels.

In at least some example contexts, the group-based communication systemmanages various entities based on an entity hierarchy. In this regard,permission data for managing one or more group-based communicationchannels may be based at least in part on the entity hierarchy Forexample, an authenticated user account may be associated with permissiondata specifically configured for managing a particular group-basedcommunication channel. Additionally or alternatively, an authenticateduser account may be associated with permission data for managing aworkspace, and in this regard the authenticated user account may bepermissioned for managing all group-based communication channels withinthe group-based workspace or a specific subset of group-basedcommunication channels within the group-based workspace. Additionally oralternatively yet, an authenticated user account may be associated withpermission data for managing an organization, and in this regard theauthenticated user account may be permissioned for managing allgroup-based communication channels within any group-based workspacesassociated with the organization. In some such circumstances, the numberof group-based communication channels manageable by an authenticateduser account is significant, such that efficient channel managementsystems are required to make such management practical and/or otherwisepossible.

Implementations of group-based communication systems often lack theability to access desired information associated with group-basedcommunication channels that a particular user may manage. Often, toaccess information associated with a group-based communication channeland/or manage the group-based communication channel, the user must firstjoin the group-based communication channel to access, and/or update,settings and/or other information for the group-based communicationchannel. In traditional implementations, additional complexity isfurther introduced in circumstances where a user desires to manage agroup-based communication channel not readily accessible via the user'sauthenticated user account. For example, in conventionalimplementations, a user desiring to manage a private group-basedcommunication channel, the user often must be invited and/or request aninvite to join the private group-based communication channel, and onlyafter successfully joining (e.g., and being configured to access theprivate group-based communication channel) can the user access thedesired information and/or update data to manage the group-basedcommunication channel. In circumstances where an authenticated useraccount is only temporarily joining the group-based communicationchannel (e.g., to manage the group-based communication channel),processing resources dedicated to the process of joining the group-basedcommunication channel are entirely wasted. Further, such a process forchannel management increases user frustration for administrators andother users involved with the process.

Embodiments herein provide apparatuses, systems, computer-implementedmethods, and computer program products for centralized channelmanagement via a group-based communication system. Some such embodimentsprovide for improved functionality for accessing and/or displayingchannel information for any number of group-based communicationchannels, for example to further enable streamlined processing and/oranalysis via a client device, for example by a user accessing the clientdevice. Additionally or alternatively, embodiments herein providefunctionality for managing any number of group-based communicationchannels, for example to manage a plurality group-based communicationchannels with reduced operations with respect to managing suchgroup-based communication channels individually. Additionally oralternatively still, some such embodiments provide functionality forconfiguring and/or causing rendering of one or more associated improveduser interfaces enabling centralized channel management of any number ofgroup-based communication channels to reduce the number of userinteractions required for managing any number of the group-basedcommunication channels. Further, by providing functionality forcentralized channel management, processing resources may be conserved bynot requiring a user join and/or access a group-based communicationchannel to manage said group-based communication channel. In thisregard, an authenticated user account may manage the group-basedcommunication channel even in circumstances where the authenticated useraccount is not associated with permission data for accessing thegroup-based communication channel, reducing the computing resourcesrequired to complete successful management of the group-basedcommunication channel, reducing user frustration, and enablingmanagement of group-based communication channel(s) in circumstanceswhere granting permission to the authenticated user account foraccessing the group-based communication channels would applicablepolicies, laws, and/or data privacy and/or data security policies.

Definitions

In some embodiments, some of the operations above may be modified orfurther amplified. Furthermore, in some embodiments, additional optionaloperations may be included. Modifications, amplifications, or additionsto the operations above may be performed in any order and in anycombination.

Many modifications and other embodiments of the disclosure set forthherein will come to mind to one skilled in the art to which thisdisclosure pertains having the benefit of the teachings presented in theforegoing description and the associated drawings. Therefore, it is tobe understood that the embodiments are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

As used herein, the terms “data,” “content,” “digital content,” “digitalcontent object,” “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present disclosure.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present disclosure. Further, where acomputing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like, sometimes referred to herein as a “network.”Similarly, where a computing device is described herein to send data toanother computing device, it will be appreciated that the data may besent directly to another computing device or may be sent indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like.

The term “identifier” refers to electronically managed information thatis uniquely correlated with (i.e., identifies) a particular data object,set of data, or information. In some embodiments, an identifier includesone or more of a binary data value, a numerical data value, ASCII text,text encoded via another encoding schema, a pointer, a memory address,or a combination thereof.

The term “client device” refers to computer hardware and/or softwarethat is configured to access a service made available by a server, suchas a group-based communication server of a group-based communicationsystem. The server is often (but not always) on another computer system,in which case the client device accesses the service by way of anetwork. Client devices may include, without limitation, smart phones,tablet computers, laptop computers, wearables, personal computers,enterprise computers, and the like. Client devices may be associatedwith a user. The association may be created by the client devicetransmitting registration information for user to the group-basedcommunication server. In some instances, a client device may betemporarily associated with a user and/or authenticated user account(e.g., only when a user is logged onto the group-based communicationsystem app). In such instances, a user may login via a client device toexecute an authenticated session via the client device and associatedwith a particular authenticated user account.

“Group-based” is used herein to refer to a system, channel, message, orvirtual environment that has security sufficient such that it isaccessible only to a defined group of users. The group may be defined bycommon access credentials such as those of an organization or commercialenterprise. Access may further be facilitated by a validated request tojoin or an invitation originated from one user who has been grantedaccess to the group to another entity who has not been granted access tothe group. Group identifiers are used to associate data, information,messages, etc., with specific groups.

The term “group-based communication system” refers to a communicationssoftware platform and associated hardware that is configured to supportand maintain a plurality of group-based communication interfaces and allassociated functionality. Group-based communication system users areorganized into organization groups (e.g., employees of differentcompanies may be separate organization groups) and each group interactswith the system via a respective group-based communication interface.For example, the group-based communication system might support, amongothers, a Slack Corporation group-based communication interface and anACME Corporation group-based communication interface.

The term “external resource” refers to a software application, program,platform, or service associated with a third-party controlled system,and that is configured for authenticated communication with agroup-based communication system to provide particular functionality toa client device connected the group-based communication system. Anexternal resource provides functionality not provided natively by thegroup-based communication system. The external resource operates on acompiled code base or repository that is separate and distinct from thatwhich supports the group-based communication system. In someembodiments, the external resource may communicate with the group-basedcommunication system, and vice versa, through one or more applicationprogram interfaces (APIs). In some embodiments, the external resourcereceives tokens and/or other authentication credentials that are used tofacilitate secure communication between the external resource and thegroup-based communication system, such as for navigating the networksecurity layers or protocols (e.g., network firewall protocols) securingthe group-based communication system. Additionally or alternatively, insome embodiments, a group-based communication system stores one or moreauthentication token(s) for accessing functionality provided by theexternal resource. In some embodiments, access to an external resourceis managed on a workspace level. In other embodiments, access toexternal resource is managed on an organization level.

The term “group-based communication interface” refers to a virtualcommunications environment configured to facilitate user interactionwith a group-based communications system. Each group-based communicationinterface is accessible and viewable to a select group of users, such asa group of employees of a business or organization (e.g., the SlackCorp. interface would be accessible and viewable to the Slack employeeshowever the ACME Corporation group-based communication interface wouldnot be accessible and viewable to Slack employees). The group-basedcommunication interface includes a plurality of group-basedcommunication channels (e.g., a marketing channel, sales channel,accounting channel, etc.). In some embodiments, a group-basedcommunication interface comprises one or more sub-interfaces, forexample a sidebar interface, content interface, and flex interface, orcombination thereof (as defined below).

The term “group-based communication channel” refers to a virtualcommunications environment or feed that is configured to displaymessaging communications posted by channel members (e.g., validatedusers accessing the environment using client devices) that are viewableonly to the members of the group. The format of the group-basedcommunication channel may appear differently to different members of thegroup-based communication channel; however, the content of thegroup-based communication channel (i.e., messaging communications) willbe displayed to each member of the group-based communication channel.For instance, a common set of group-based messaging communications willbe displayed to each member of the respective group-based communicationchannel such that the content of the group-based communication channel(i.e., messaging communications) will not vary per member of thegroup-based communication channel. In some embodiments, a group-basedcommunication system is configured to manage various types ofgroup-based communication channels, which may be identified based on a“group-based communication channel type.” Non-limiting examples ofgroup-based communication channels include a single-user directgroup-based communication channel (e.g., for communications between twoauthenticated user accounts), a multi-user direct group-basedcommunication channel (e.g., for communications between a plurality ofauthenticated user accounts), a public group-based communication channel(e.g., accessible to all authenticated user accounts within aworkspace), a private group-based communication channel (e.g.,accessible to invited and/or specific authenticated user accounts withina workspace), an external resource group-based communication channel(e.g., for communications from and/or to an external resource accessiblewithin a workspace or organization), or any combination thereof. Theterm “group-based communication channel set” refers to any number ofgroup-based communication channels. A group-based communication channelset may be grouped by any parameter value for one or more parameters ofa group-based communication channel.

In some embodiments, one group-based communication channel may beassociated with one or more organization identifiers and/or workspaceidentifiers. In this regard, the group-based communication channel maybe accessible to multiple organizations and/or workspaces. A group-basedcommunication channel associated with more than one organizationidentifiers and/or workspace identifiers is a “common group-basedcommunication channel.”

The terms “group-based communication channel identifier” and “channelidentifier” refer to one or more identifiers by which a group-basedcommunication channel may be uniquely identified by a group-basedcommunication system. A group-based communication channel identifierassociated with a common group-based communication channel is a “commongroup-based communication channel identifier.”

The term “channel owner data” refers to electronically managedinformation associated with a group-based communication channel thatrepresents one or more authenticated user account identifiers, orcorresponding authenticated user account information, that indicates theauthenticated user account created and/or is otherwise permissioned formanaging access to, information within, and/or sharing of thegroup-based communication channel. In some embodiments, the channelowner data identifies a single authenticated user account that createdthe group-based communication channel, or a single authenticated useraccount designated as a primary owner of the group-based communicationchannel. In other embodiments, the channel owner data identifies aplurality of authenticated user accounts that created and/or weredesignated a primary owner of the group-based communication channel.

The term “delegated management data” refers to electronically managedinformation associated with a group-based communication channel thatrepresents one or more authenticated user account identifiers, orcorresponding user account information, that indicates the authenticateduser account has been permissioned by a primary owner for managingaccess to, information within, and/or sharing of the group-basedcommunication channel. In some embodiments, for a particular group-basedcommunication channel, a channel primary owner, as indicated by channelowner data for the group-based communication channel, is permissioned toset delegated management data for the group-based communication channel.For example, an authenticated user account indicated by the channelowner data may update the channel owner data to add one or more newauthenticated user account(s) (e.g., to permission for managing thegroup-based communication channel) and/or remove one or moreauthenticated user account(s) (e.g., to remove permission for managingthe group-based communication channel).

The term “channel creation timestamp data” refers to metadata associatedwith a group-based communication channel that indicates a date, time,and/or datetime at which the group-based communication channel wascreated. In some embodiments, a group-based communication systemgenerates and/or otherwise identifies channel creation timestamp datafor assigning to a newly generated group-based communication channelupon receiving a new channel request, for example from one or moreclient devices. It should be appreciated that the channel creationtimestamp data may be embodied in any of a myriad of formats, timezones, and level of details.

The term “channel creator account data” refers to electronically managedinformation representing one or more authenticated user accountidentifiers, information, and/or the like, for authenticated useraccount(s) that requested creation of the group-based communicationchannel. In some embodiments, for example, a group-based communicationsystem receives a channel creation request from a client deviceassociated with an authenticated user account during a previouslyinitiated authenticated session. In some such embodiments, thegroup-based communication system may identify the channel creatoraccount data from the received channel creation request, such that thedata may be assigned to the newly created group-based communicationchannel.

The term “channel private status data” refers to electronically managedinformation, associated with a group-based communication channel, thatindicates whether the group-based communication channel is a privategroup-based communication channel. In some embodiments, the value ofchannel private status data indicates whether the associated group-basedcommunication channel is a private group-based communication channel,for example where a first value indicates the channel is private and asecond value indicates a channel is public.

The term “channel archive status data” refers to electronically managedinformation, associated with a group-based communication channel, thatindicates whether the group-based communication channel is archived. Agroup-based communication channel that is archived may be stored suchthat group-based communication messages stored associated with thegroup-based communication channel are stored indefinitely, and/or storedsubject to data retention policies different from default retentionpolicies for the group-based communication channel. In some embodiments,the value of channel archive status data indicates whether theassociated group-based communication channel is archived, for examplewhere a first value indicates the channel is archived and a second valueindicates a channel is not archived.

The term “channel workspace data” refers to electronically managedinformation indicating workspaces providing access to, including, and/orotherwise associated with, a group-based communication channel, and/orsummary data associated with such workspace(s). In some embodiments, forexample, channel workspace data includes workspace identifiers for eachworkspace the group-based communication channel is accessible within(e.g., an owner workspace and/or any workspace with which the channel isshared), data indicating a count of the workspaces the group-basedcommunication channel is accessible within, or any combination thereof.

The term “channel organization-sharing status data” refers to dataindicating whether a group-based communication channel is associatedwith all workspaces of a particular organization. In some embodiments,channel organization-sharing status data includes data indicatingwhether the group-based communication channel is an organization-widechannel (e.g., accessible in all workspaces of an organization), dataindicating whether the group-based communication channel is anorganization-wide default channel, or any combination thereof.

The term “channel member count data” refers to electronically managedinformation identifying a number of members having access to agroup-based communication channel. In some embodiments, channel membercount data includes “authenticated account member data” indicating thenumber of authenticated user accounts having access to the group-basedcommunication channel, and/or “guest account member data” indicating thenumber of guest user accounts having access to the group-basedcommunication channel.

The term “historical activity data” refers to electronically managedinformation associated with a group-based communication channel thatsummarizes various user-performed actions within the group-basedcommunication channel. In some embodiments, historical activity dataincludes one or more of: a number of group-based communication messagesposted within the group-based communication channel, a number ofexternal resource requests within the group-based communication channel,a number of members that have posted to the group-based communicationchannel within a particular timeframe (or for the lifetime of thechannel), and/or the like. In some embodiments, historical activity dataadditionally or alternative includes last activity data indicating thelast management action performed for the group-based communicationchannel.

The term “channel share status data” refers to electronically managedinformation associated with a group-based communication channelrepresenting whether the group-based communication channel has beenshared with one or more organizations and/or other workspaces. In someembodiments, the channel share status data includes one or moreidentifiers associated with the organization(s) and/or workspace(s) withwhich the group-based communication channel has been shared (if any).

The term “channel guest status data” refers to electronically managedinformation associated with a group-based communication channelrepresenting whether the group-based communication channel is configuredto allow guest authenticated user accounts to access the group-basedcommunication channel. In some embodiments, the channel guest statusdata includes one or more authenticated user account identifiers, and/orcorresponding authenticated user account information, representing theguest user account(s) that have been added to the group-basedcommunication channel (if any).

The terms “workspace data object,” “group-based workspace,” and“workspace” refer to electronically managed data including a group ofgroup-based communication channels and authenticated user accountspermissioned to access one or more of the group-based communicationchannels therein. In some embodiments, a workspace data object isconfigured to enable one or more authenticated user account(s)permissioned as administrators to manage access to the workspace, forexample to invite one or more authenticated user account(s) to accessthe workspace and/or terminate access rights to one or moreauthenticated user account(s) previously invited to the workspace. Theterm “workspace identifier” refers to one or more identifiers by which aworkspace within a group-based communication system may be uniquelyidentified. An organization or other entity within a group-basedcommunication system may be associated with any number of workspaceidentifiers.

The term “workspace identifier” refers to one or more identifiers bywhich a workspace within a group-based communication system may beuniquely identified. An organization or other entity within agroup-based communication system may be associated with any number ofworkspace identifiers.

The term “organization” refers to one or more data structures by which aset of workspaces and/or group-based communication channels areassociated with a particular entity. The term “organization identifier”refers to one or more items of data by which an organization may beuniquely identifier. A non-limiting example of an organizationidentifier comprises American Standard Code for Information Interchange(ASCII) text, a pointer, a memory address, a unique numerical and/orstring value, and the like.

The term “user” refers to an individual, group of individuals, business,organization, and the like. Users referred to herein are discussedlargely in connection with client device enabled activity for accessinga group-based communication interface (or set of group-basedcommunication interfaces) of a group-based communication system. A usermay be associated with one or more authenticated user accounts, asdefined herein.

The term “authenticated user account” refers to informationcorresponding to authentication credentials (e.g., a username andpassword combination) for accessing particular functionality of agroup-based communication system. An authenticated user account isassociated with any of a variety of information, including, for exampleand without limitation, a user identifier, one or more group-basedcommunication channel identifiers associated with group-basedcommunication channels that the user has been granted access to (i.e.,accessible group-based communication channels), one or more groupidentifiers for workspaces with which the user is associated (e.g.,accessible workspaces), one or more organization identifiers fororganizations with which the user is associated, an indication as towhether the user is an owner of any group-based communication channels,an indication as to whether the user has any group-based communicationchannel restrictions, a plurality of group-based communication messages,an emoji, a plurality of conversations, a plurality of conversationtopics, an avatar, an email address, a real name (e.g., John Doe), ausername (e.g., jdoe), a password, a real name, a time zone, a status,and the like. In some embodiments, a user utilizes a client device totransmit authentication credentials corresponding to a particularauthenticated user account to a group-based communication system, and inresponse initiates an authenticated session configured to enable accessto functionality and/or information accessible to the authenticated useraccount via the client device during the authenticated session.

The term “permission data” refers to one or more data indicatorsassociated with authenticated user account access to functionalityassociated with a group-based communication channel, workspace,organization, and/or other entity. For example, in some embodiments,permission data represents whether an authenticated user account ispermissioned to access a group-based workspace and/or group-basedcommunication channel. Additionally or alternatively, in someembodiments, permission data represents whether an authenticated useraccount is permissioned to manage one or more settings of a group-basedcommunication channel, manage access to a group-based communicationchannel, and/or share a group-based communication channel. In someembodiments, an authenticated user account is permissioned via one ormore existing admin accounts to access one or more workspaces associatedwith a particular organization. Additionally or alternatively, in someembodiments, an authenticated user account is permissioned to access oneor more group-based communication channels of a particular workspace.

It should be appreciated that one or more entities may be associatedwith a myriad of permission data associated with various functionality.For example, in some embodiments, an organization is associated withorganization-level permission data, such as permission data for settingauthenticated user account(s), and/or groups thereof, having access tofunctionality for managing group-based communication channels of variouschannel types, for accessing one or more workspaces and/or group-basedcommunication channels associated with the organization, for sharing aworkspace and/or group-based communication channel, and/or forconfiguring a group-based communication channel as a private group-basedcommunication channel or public group-based communication channel. Insome such embodiments, a group-based communication system similarlystores such permission data on a workspace-level, such that access tosuch functionality may be determined on a per-workspace basis.Additionally or alternatively, in some such embodiments, a group-basedcommunication system similarly stores such permission data on achannel-level, such that access to such functionality may be determinedon a per-channel basis. In some embodiments, certain permission dataoverrides other permission data, for example where permission dataassociated with higher-level entities is overridden by permission dataassociated with a lower-level entity (e.g., permission data associatedwith a group-based communication channel overrides permission dataassociated with the organization linked to the group-based communicationchannel).

The term “workspace management permission data” refers to one or moredata objects and/or values, linked to an authenticated user account andassociated with a workspace identifier, that indicates the authenticateduser account is permissioned to access the workspace identified by theworkspace identifier. In some embodiments, another authenticated useraccount previously permissioned to manage the workspace or associatedorganization is configured to assign workspace management permissiondata to one or more other authenticated user accounts.

The term “organization management permission data” refers to one or moredata objects and/or values, linked to an authenticated user account andassociated with an organization identifier, that indicates theauthenticated user account is permissioned to access the some or allworkspaces associated with the organization identified by theorganization identifier. In some embodiments, another authenticated useraccount previously permissioned to manage the organization is configuredto assign organization management permission data to one or more otherauthenticated user accounts.

The term “inaccessible group-based communication channel” refers to agroup-based communication channel that an authenticated user account hasnot joined and/or otherwise is not permissioned to access. In someembodiments, a group-based communication channel is an inaccessiblegroup-based communication channel with respect to a particularauthenticated user account in a circumstance where the authenticateduser account is not associated with any permission data for accessingthe group-based communication channel.

The term “manageable group-based communication channel” refers to agroup-based communication channel configured to be managed by anauthenticated user account. In some embodiments, a group-basedcommunication channel is identifiable as a manageable group-basedcommunication channel, with respect to a particular authenticated useraccount, in a circumstance where the authenticated user account isassociated with permission data for managing the group-basedcommunication channel, and/or associated with permission data formanaging a higher-level entity associated with the group-basedcommunication channel (e.g., a workspace and/or organization). The term“manageable group-based communication channel set” refers to any numberof manageable group-based communication channel(s) configured formanagement by an authenticated user account. In some embodiments, amanageable group-based communication channel set includes allgroup-based communication channels configured for management by anauthenticated user account.

The term “centralized channel data” refers to information associatedwith one or more group-based communication channels permissioned formanagement by one or more authenticated user accounts. In some contexts,for example where the authenticated user account is permissioned as aworkspace-level administrator, the centralized channel data includesinformation for group-based communication channels associated with asingle workspace that the authenticated user account is permissioned tomanage. In other contexts, for example where the authenticated useraccount is permissioned as an organization-level administrator, thecentralized channel data includes information for one or moregroup-based communication channels for all workspaces associated with anorganization that the authenticated user account is permissioned tomanage.

The term “group-based communication channel metadata set” refers toinformation included with, derived from, and/or otherwise associatedwith a group-based communication channel. For example, in someembodiments, a group-based communication channel metadata set includesinformation to be rendered to one or more interfaces, and/or to beprocessed for rendering to one or more interfaces. Non-limiting examplesof a group-based communication channel metadata set includes: channelcreation timestamp data, channel creator account data, historicalactivity data, channel share status data, channel guest status data, achannel user count, a channel message count, and channel integrationsdata associated with one or more external resources.

The term “centralized channel management dashboard” refers to aspecially configured user interface including centralized channel dataassociated with at least one authenticated user account. In someembodiments, the centralized channel management dashboard is configuredto include one or more group-based communication channel metadata set(s)for group-based communication channels that the authenticated useraccount is permissioned to manage. Additionally or alternatively, insome embodiments, the centralized channel management dashboard includesone or more channel management action interface elements.

The term “centralized channel management request” refers toelectronically managed data transmitted from a client device to agroup-based communication system indicating a user request for receivingchannel information associated with any of group-based communicationchannels manageable by an authenticated user account. In someembodiments, response data received in response to the centralizedchannel management request is configured to cause rendering of acentralized channel dashboard to a display associated with the clientdevice. In some embodiments, the centralized channel management requestincludes at least an authenticated user account identifier and/or otherdata for use in retrieving manageable group-based communication channelsfor rendering via a centralized channel management dashboard, orassociated data for use in rendering the corresponding centralizedchannel dashboard.

The term “channel management action” refers to one or more processes forupdating data embodying or associated with a group-based communicationchannel to change access to, storage of, and/or other functionalityassociated with the group-based communication channel. In someembodiments, a channel management action is initiated by a group-basedcommunication system in response to receiving a “channel managementrequest.” In some embodiments, the channel management action includesone or more identifiers uniquely identifying the channel managementaction to be initiated.

The term “channel posting rule action” refers to a channel managementaction for updating electronically managed information associated with agroup-based communication channel to alter rules for posting group-basedcommunication messages to the channels by members of the group-basedcommunication channel. In at least one example context, a channelposting rule action alters one or more setting parameter value(s)associated with the group-based communication channel to limit postingonly to specific user groups (e.g., administrator user accounts only, adefined authenticated user account and/or guest account group only, orthe like), types of group-based communication message that may be postedwithin the group-based communication channel (e.g., image messages only,external resource messages only, and/or the like), and/or restrictingattachments to group-based communication messages (e.g., no messageswith attachments may be posted within the group-based communicationchannel). It should be appreciated that a channel posting rule actionmay change one or more values to effect any desired change in broadeningand/or narrowing one or more restrictions on posting group-basedcommunication messages within a group-based communication channel.

The term “user access action” refers to a channel management action forupdating electronically managed data associated with permission toaccess a group-based communication channel. For example, in someembodiments, a user access action includes generating permission dataassociated with one or more authenticated user accounts to grant accessto the group-based communication channel, and/or revoking permissiondata associated with one or more authenticated user accounts to revokeaccess to the group-based communication channel. Additionally oralternatively, in some embodiments, a user access action grants and/orrevokes access to a group-based communication channel for one or moreguest user accounts.

The term “channel defaulting action” refers to a channel managementaction for updating electronically managed information associated with agroup-based communication channel for setting default access to thegroup-based communication channel within a particular workspace, subsetof workspaces, and/or all workspaces for an organization. In someembodiments, for example, a channel defaulting action includes settingone or more electronic data values indicating whether the group-basedcommunication channel should be provided as a default within one or moreworkspaces.

The term “channel archive action” refers to a channel management actionfor updating electronically managed data associated with storing agroup-based communication channel as archived. In some embodiments, achannel archive action includes setting one or more electronic datavalues indicating whether the group-based communication channel shouldbe stored as archived. In some embodiments, in a circumstance where agroup-based communication channel is indicated for storing as archived,group-based communication messages stored associated with thegroup-based communication channel (e.g., posted within the group-basedcommunication channel) are backed up in a second storage by agroup-based communication system, and/or are stored according to asecond data retention policy different than a default data retentionpolicy (e.g., to be stored indefinitely rather than deleted after acertain time period).

The term “channel rename action” refers to a channel management actionfor updating electronically managed data representing a useridentifiable name for a group-based communication channel. In someembodiments, a channel rename action includes updating a data value fora name parameter stored associated with the group-based communicationchannel.

The term “channel share action” refers to a channel management actionfor updating whether a group-based communication channel is shared withone or more third-party organizations, and/or with one or more otherworkspaces associated with an owner organization for the group-basedcommunication channel. In some embodiments, a channel share actionincludes granting and/or revoking permission data for one or morethird-party organizations, such that authenticated user accountsassociated with the third-party organization(s) are permissioned toaccess the group-based communication channel and/or revoke suchpermission to access the group-based communication channel. Additionallyor alternatively, in some embodiments, a channel share action includesgranting and/or revoking permission data for one or more otherworkspaces for an organization, such as an owner organization,associated with the group-based communication channel, such thatauthenticated user accounts permissioned to access the workspace(s) withwhich the group-based communication channel is shared may further accessthe group-based communication channel.

The term “channel delete action” refers to a channel management actionfor updating the existence of a group-based communication channel. Insome embodiments, a channel delete action includes deleting data recordsembodying the group-based communication channel, and/or group-basedcommunication messages associated with the group-based communicationchannel, from one or more datastores. Alternatively or additionally, insome embodiments, a channel delete action includes making data embodyingthe group-based communication channel, and/or group-based communicationmessages associated with the group-based communication channel,inaccessible. In yet some other embodiments, a channel delete actionincludes marking one or more group-based communication channels fordeletion at another time (e.g., after a set time period), which may ormay not be revocable to restore the group-based communication channel.

The term “channel management action interface element” refers to one ormore components of an interface configured to initiate one or moregroup-based communication channel management actions. In someembodiments, a channel management action interface element is configuredto receive user interaction indicating a user desire to initiate anassociated action. In some embodiments, a channel management actioninterface element is rendered for a specific channel management action(e.g., a delete button, a rename button, and the like). In otherembodiments, a channel management action interface element is renderedto provide sub-interfaces each associated with a particular channelmanagement action interface element (e.g., a dropdown menu, modalinterface, and/or the like).

The term “channel management data” refers to electronically managedinformation representing a user request to perform one or more channelmanagement actions, and that includes one or more data parameters forprocessing to execute the channel management action. In someembodiments, channel management data is transmitted from a client deviceto a group-based communication system in response to user interactionwith a channel management action interface element. In some embodiments,channel management data includes at least an action identifier thatrepresents the requested type of channel management action requested(e.g., a channel rename action, channel delete action, or the like).Additionally or alternatively, in some embodiments, channel managementdata includes at least a channel identifier for a group-basedcommunication channel associated with the channel management data.

The term “user interaction” refers to user engagement with a clientdevice, peripheral, and/or associated interface. Non-limiting examplesof user interactions include user engagement of a touch area or touchscreen, a tactile gesture (e.g., swipe, long press, and the like), amotion gesture (e.g., moving the user's body and/or a device in apredefined motion), a virtual button press, a mouse click, a scroll, akeyboard press, a peripheral button press, a controller input, ajoystick input, a voice command or other audio interaction, a remotecontrol input, and/or or a combination thereof. In some embodiments,user interaction is associated with particular functionality based on acurrently rendered user interface, for example based on a locationand/or type of user interaction performed. The term “user interactiondata” refers to data generated based on a user interaction. In someembodiments, user interaction data is processable by a processor and/orcorresponding circuitry, to identify the user interaction and/orassociated data objects, and/or process the associated data objects.

The term “channel privacy access data” refers to electronically managedinformation, associated with a group-based communication channel,representing the organizations, authenticated user accounts, externalresources, and/or other entities that have access to group-basedcommunication messages within the group-based communication channel. Inthis regard, in some embodiments, the channel privacy access dataincludes any number of authenticated user account identifiers,organization identifiers, workspace identifiers, external resourceidentifiers, and/or the like. In some embodiments, a group-basedcommunication system is configured to derive channel privacy access datafor a particular group-based communication channel based on the channeltype, one or more permissions settings, channel share status data,authenticated user account permission data, and/or any combinationthereof.

The term “selected channel information request” refers to electronicallymanaged information indicating a user request for channel privacy accessdata associated with a group-based communication channel. In someembodiments, the selected channel information request is transmittedfrom a client device to a group-based communication system, for examplein response to user interaction via the client device. In someembodiments, a selected channel information request includes at least agroup-based communication channel identifier associated with thegroup-based communication channel for which channel privacy access datais to be retrieved.

The term “channel privacy notification information” refers to channelprivacy access data, a subset of channel privacy access data, associateddata, and/or data derived therefrom, for rendering associated with agroup-based communication channel to an interface by a client device. Insome embodiments, channel privacy notification information includeshuman-readable text representing entities having access to thegroup-based communication channel based on corresponding channel privacyaccess data. Additionally or alternatively, in some embodiments, channelprivacy notification information includes one or more images forrendering associated with the group-based communication channel, forexample avatar images and/or profile images associated withauthenticated user accounts, workspaces, organizations, and/or the like,having access to the group-based communication channel.

Example System Architecture of Embodiments

The methods, apparatuses, systems, and computer program products of thepresent disclosure may be embodied by any variety of devices. Forexample, a method, apparatus, system, and computer program product of anexample embodiment may be embodied by a fixed computing device, such asa personal computer, computing server, computing workstation, or acombination thereof. Further, an example embodiment may be embodied byany of a variety of mobile terminals, mobile telephones, smartphones,laptop computers, tablet computers, or any combination of theaforementioned devices.

In this regard, FIG. 1 discloses an example computing system in whichembodiments of the present disclosure may operate. FIG. 1 illustrates anoverview for a system configured for centralized channel management.Specifically, the system includes a plurality of external resources,specifically external resource 106A, external resource 106B, andexternal resource 106C (collectively “external resources 106”).Additionally, as illustrated, the system includes a plurality of userdevices, specifically client device 104A, client device 104B, and clientdevice 104C (collectively “client devices 104”). Additionally, asillustrated, the system includes group-based communication system 102.The group-based communication system 102 is in communication with theexternal resources 106 and the client devices 104 over a communicationsnetwork, specifically communications network 108.

The group-based communication system 102 comprises a group-basedcommunication server 102A (“server 102A”) and a group-basedcommunication datastore 102B (“datastore 102B”). The server 102A may beconfigured to communicate with the datastore 102B to enable thegroup-based communication system 102 to provide the functionalitydescribed herein. In some embodiments, the server 102A and datastore102B are connected within one or more local environment, for example ata location controlled an owner and/or controller of the group-basedcommunication system 102. In yet other embodiments, the server 102A andthe datastore 102B are located remotely from one another, and/or includeone or more cloud environments separate from one another.

The server 102A may be embodied by a computer or a plurality ofcomputers. The server 102A may provide various functionality associatedwith receiving group-based communication messages or data associatedtherewith, generating, storing, and/or maintaining group-basedcommunication messages, and/or transmitting group-based communicationmessages to one or more client device(s), such as the client devices104. Additionally or alternatively, in some embodiments, the server 102Aprovides various additional functionality through communication with oneor more external resources, such as the external resources 106. In somesuch embodiments, the server 102A communicates with any of the externalresources 106 to facilitate transmission of external resourceinformation to one or more client device(s), which may be transmittedvia one or more group-based communication interfaces automatically or inresponse to a user request. For example, the server 102A may be operableto receive and post, or transmit, group-based communication messagesprovided by one or more of the client devices 104 and/or externalresources 106 to a group-based communication channel, and perform one ormore associated actions accordingly.

Additionally or alternatively, in some embodiments, the server 102A isconfigured to enable centralized channel management of one or moregroup-based communication channels. In this regard, the server 102A maybe configured to authenticate a user identity associated with a user ofone of the client devices 104, for example to initiate an authenticatedsession associated with an authenticated user account. Further, theserver 102A may be configured to identify one or more group-basedcommunication channels that the authenticated user account ispermissioned for managing, and in some embodiments to provide some suchinformation to the client device. In this regard, the server 102A mayprocess one or more requests and provide corresponding informationassociated with functionality for managing the group-based communicationchannels provided as associated with the authenticated user account. Insome such embodiments, the server 102A configures and/or otherwisecauses rendering of one or more interfaces associated with suchfunctionality. For example, in some embodiments, the server 102A isconfigured to, during an authenticated session associated with anauthenticated user account, cause rendering of one or more group-basedcommunication interfaces including group-based communication channelsassociated with permission data for management by the authenticated useraccount, and/or for performing one or more actions for any number ofgroup-based communication channels included in the interface. In somesuch embodiments, the one or more group-based communication interfacesincludes one or more interface elements for manipulating the datadisplayed associated with the identified group-based communicationchannels. For example, the server 102A may be configured to enablefiltering of the identified group-based communication channels,performing one or more actions for a subset of the group-basedcommunication channels (e.g., all group-based communication channelsassociated with one or more parameter values, including a channel type,associated workspace identifier, sharing permissions, or the like). Itshould be appreciated that the server 102A may be configured to causerendering of a group-based communication interface, and/or one or moreassociated interfaces, comprising one or more user interface elementsfor performing any of the functionality for centralized channelmanagement described herein, alone or in any combination with otherinterface elements for other functionality described herein.

The datastore 102B may be embodied as any number of data storagedevices, such as one or more local storage device(s), cloud storagedevice(s), network attached storage (“NAS”) device or a plurality of NASdevices, or as a separate database server of plurality of servers. Thedatastore 102B includes information accessed by, received by, and/orotherwise generated and/or processed by the server 102A to facilitatefunctionality provided by the group-based communication system 102. Forexample, the datastore 102B may be configured to store, withoutlimitation, a plurality of group-based communications associated with aplurality of workspaces, group-based communication channels,authenticated user accounts, external resources, and/or the like.Additionally or alternatively, the datastore 102B may be configured tostore authentication credentials associated with various authenticateduser accounts, for example to enable a client device to initiate anauthenticated session with the group-based communication system 102 viaone or more authentication processes, such as by providing theauthentication credentials and comparing to the stored authenticationcredentials, and to link the client device with an authenticated useraccount for enabling the authenticated session.

In some embodiments, the datastore 102B is configured at least forstoring data associated with administrator permissions for one or moreauthenticated user accounts, and for the hierarchy of entities to enablefunctionality of the group-based communication system 102. For example,in at least some embodiments, the datastore 102B configured to store atleast one or more organizations associated with one or more workspaces,the workspaces stored further associated with one or more group-basedcommunication channel accessible therein, and each authenticated useraccount associated with data indicating whether the authenticated useraccount has been given permissions as an administrator user account forone or more of the organization, workspace, and/or group-basedcommunication channels. In this regard, the datastore 102B is configuredto enable identification of one or more group-based communicationchannels permissioned for management by a particular authenticated useraccount. In some such embodiments, the datastore 102B is configured tobe queried to retrieve such information for a particular authenticateduser account, for example using a user account identifier for theauthenticated user account. In at least one example context, the server102A is configured to communicate with the datastore 102B for performingsuch a query for each user that accesses centralized channel managementfunctionality of the server 102A.

Each of the client devices 104 may be embodied by any of a variety ofcomputing devices as defined above. Electronic data received by thegroup-based communication server 102A from the client devices 104 may beprovided in various forms and via various methods for processing. Forexample, the client devices 104 may include desktop computers, laptopcomputers, smartphones, netbooks, tablet computers, wearables, and/orthe like. Each of the client devices 104 may include a networkinginterface to enable such communications, and/or each of the clientdevices 104 may be associated with a device configured with a networkinterface to enable such communications (e.g., a wearable deviceconnected to a smartphone). The client devices 104 may be configured toenable communications over various networks utilizing various networkinghardware, software, and/or firmware (e.g., Bluetooth between asmartphone and associated wearable, a carrier network between asmartphone and a group-based communication system and/or between awearable and a group-based communication system, and/or one or morewireless and/or wireless networks for communicating via the Internetbetween a client device and a group-based communication system).

In an example context, the client devices 104 may execute an applicationor “app” to enable interaction with the group-based communication system102. Such applications are typically designed for execution via acomputing device dependent on the operating system and/or otherconfigurations associated with the computing device. For example, anapplication may be provided that executes on mobile device operatingsystems such as iOS®, Android®, or Windows®. Alternatively, anapplication may be provided that executes on a personal computeroperating system, such as Windows®, macOS®, Linux®, or another operatingsystem executed on a laptop device, desktop device, or terminal device.These platforms typically provide frameworks that allow applications tocommunicate with one another and/or with particular hardware and/orsoftware components of the client device. For example, the mobileoperating systems and/or personal computer operating systems named aboveeach provide frameworks for interacting with location servicescircuitry, wired and/or wireless network interfaces, user contacts, andother applications. In an example context, the application is embodiedby a group-based communication service application provided by thegroup-based communication system. Communication with hardware andsoftware modules outside of the application is typically provided viaone or more application programming interfaces (APIs) configured by theoperating system for the client device and/or provided via an externalresource.

Alternatively or additionally, the client devices 104 may interact withthe group-based communication system 102 via a web application. In anexample context, the web application is embodied by a web browserexecuted via one of the client devices 104. As yet another example, theclient devices 104 may include various hardware, firmware, and/orsoftware designed to interface with the group-based communication system102. Each of the client devices 104 may be associated with anauthenticated session, for example after a user undergoes one or moreauthentication processes, that links each of the client devices 104 witha corresponding authenticated user account for the duration of theauthenticated session. It should be appreciated that, in someembodiments, any of the client devices 104 may be used to access dataassociated with any authenticated account upon providing the requisiteauthentication credentials for the authenticated user account (e.g., ausername and password combination) or by completing any otherauthentication process.

Each of the external resources 106 represents an external system,resource, service, software application, computer, and/or the like, thatis accessible by a group-based communication system 102 for providingassociated functionality to one or more of the client devices 104 duringan authenticated session. In some embodiments, one or more of theexternal resources 106 (or a specific subset thereof) provide specificfunctionality via one or more group-based communication interfacesprovided by the group-based communication system 102 and rendered to oneor more of the client devices 104. For example, the group-basedcommunication system 102 may access functionality provided by each ofthe external resources 106 via one or more APIs. An external resource ofthe external resources 106 may provide specific functionality and/or aspecific service integrated into a group-based communication interface.In one example, one or more of the external resources 106 may be avalidated software source code repository, or the like, which members ofa particular group-based communication workspace may collectively accessas they collaborate to develop a new software application. Additionallyor alternatively, in another context, one of the external resources 106may provide cloud storage for documents and/or the like. An externalresource of the external resources 106 may be embodied in a variety ofways utilizing a variety of computing devices, for example an externalserver remote from the group-based communication system 102 andaccessible using transmissions over the communications network 108(e.g., over the Internet, for example).

In some embodiments, group-based communication system is configured toaccess an external resource of the external resources 106 utilizing anexternal resource identifier. The external resource identifier mayinclude, or otherwise be associated with and retrievable together with,an external resource access token associated with the external resourceand/or a corresponding group-based communication system, workspace,and/or authenticated user account. A group-based communication system102 may store one or more external resource identifiers including orassociated with external resource access token(s) to enable API requeststo the external resource, which may be tied with a specific externalresource user account linked to a particular authenticated user account.For example, in this regard, an authenticated user account of thegroup-based communication system may be linked to a particular externalresource user account, such that a user may access personalized externalresource functionality.

In some embodiments, user may access an external resource 106 via one ormore workspaces and/or specific group-based communication channelsmaintained by the group-based communication system 102. In this regard,a user may add an external resource of the external resources 106 to aworkspace to make functionality associated with the external resourceaccessible from within the workspace. To provide such functionality, theuser may communicate with the group-based communication system 102 tocause the group-based communication system to communicate with theexternal resource to access such functionality. The group-basedcommunication system 102 thus enables the user to access externalresource functionality without requiring direct communication with theexternal resources 106, and may make the functionality of the externalresources 106 accessible via communications to one or more group-basedcommunication channels.

In some embodiments of an exemplary group-based communication system102, a group-based communication message may be sent from a clientdevice of the client devices 104 to a group-based communication system102. In various implementations, the group-based communication messagemay be sent to the group-based communication system 102 overcommunications network 108, for example directly by one of the clientdevices 104. In other embodiments, the group-based communication messagemay be sent to group-based communication system 102 via one or moreintermediaries, such as a messaging server, relay server, and/or thelike. In at least one example implementation, the group-basedcommunication message may include data such as a message identifier,sender/author account identifier, a group identifier, a group-basedcommunication channel identifier, communication content data (e.g.,text, emojis, images, links), attachment data (e.g., files),communication hierarchy data (e.g., the group-based communicationmessage may be a reply to another group-based communication),third-party metadata (e.g., an external resource identifier), externalresource content, and/or the like.

In one embodiment, one of the client devices 104 may provide thefollowing example group-based communication substantially in the form ofa (Secure) Hypertext Transfer Protocol (“HTTP(S)”) POST messageincluding eXtensible Markup Language (“XML”) formatted data, embodying aparticular request for authenticating user account details to initiatean authenticated session, as provided below:

POST /authrequest.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <auth_request>  <timestamp>2020-12-31 23:59:59</timestamp> <user_accounts_details>  <user_account_credentials>   <user_name>ID_user_1</user_name>    <password>abc123</password>   //OPTIONAL <cookie>cookieID</cookie>   //OPTIONAL   <digital_cert_link>www.mydigitalcertifi-cate.com/JohnDoeDaDoeDoe@gmail.com/mycertifcate.dc</ digital_cert_link>   //OPTIONAL <digital_certificate>_DATA_</digital_certificate> </user_account_credentials>  </user_accounts_details>  <client_details>//iOS Client with App and Webkit    //it should be noted that althoughseveral client details    //sections are provided to show examplevariants of client    //sources, further messages will include only oneto save    //space  <client_IP>10.0.0.123</client_IP> <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 like Mac OSX) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201Safari/9537.53</user_agent_string> <client_product_type>iPhone6,1</client_product_type> <client_serial_number>DNXXX1X1XXXX</client_serial_number> <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</ client_UDID> <client_OS>iOS</client_OS> <client_OS_version>7.1.1</client_OS_version>  <client_app_type>app withwebkit</client_app_type>  <app_installed_flag>true</app_installed_flag> <app_name>nickname.app</app_name>  <app_version>1.0 </app_version> <app_webkit_name>Mobile Safari</client_webkit_name> <client_version>537.51.2</client_version>  </client_details> <client_details> //iOS Client with Webbrowser <client_IP>10.0.0.123</client_IP>  <user_agent_string>Mozilla/5.0(iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML,like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string> <client_product_type>iPhone6,1</client_product_type> <client_serial_number>DNXXX1X1XXXX</client_serial_number> <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</ client_UDID> <client_OS>iOS</client_OS> <client_OS_version>7.1.1</client_OS_version>  <client_app_type>webbrowser</client_app_type>  <client_name>Mobile Safari</client_name> <client_version>9537.53</client_version>  </client_details> <client_details> //Android Client with Webbrowser <client_IP>10.0.0.123</client_IP>  <user_agent_string>Mozilla/5.0(Linux; U; Android 4.0.4; en-us; Nexus S Build/IMM76D)AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 MobileSafari/534.30</user_agent_string>  <client_product_type>NexusS</client_product_type> <client_serial_number>YXXXXXXXXZ</client_serial_number> <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID> <client_OS>Android</client_OS> <client_OS_version>4.0.4</client_OS_version>  <client_app_type>webbrowser</client_app_type>  <client_name>Mobile Safari</client_name> <client_version>534.30</client_version>  </client_details> <client_details> //Mac Desktop with Webbrowser <client_IP>10.0.0.123</client_IP>  <user_agent_string>Mozilla/5.0(Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.75.14 (KHTML, likeGecko) Version/7.0.3 Safari/537.75.14</user_agent_string> <client_product_type>MacPro5,1</client_product_type> <client_serial_number>YXXXXXXXXZ</client_serial_number> <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID> <client_OS>Mac OS X</client_OS> <client_OS_version>10.9.3</client_OS_version>  <client_app_type>webbrowser</client_app_type>  <client_name>Mobile Safari</client_name> <client_version>537.75.14</client_version>  </client_details> <message>  <message_identifier>ID_message_10</message_identifier> <team_identifier>ID_team_1</team_identifier> <channel_identifier>ID_channel_1</channel_identifier>  <bodycontents>That is an interesting invention. I have attached a copy ourpatent policy.</body contents> <attachments>patent_policy.pdf</attachments>  </message></auth_request>

The group-based communication system 102 comprises at least onegroup-based communication server 102A that may create a storage requestdata object based upon the received message to facilitate messageindexing and storage in a group-based communication datastore 102B. Inone implementation, the storage request data object may include datasuch as a communication identifier, a group identifier, a group-basedcommunication channel identifier, a sending user account identifier,topics, responses, communication contents (i.e., body contents),attachments, communication hierarchy data, third party metadata,conversation primitive data, and/or the like. For example, thegroup-based communication server 102A may provide the following examplestorage request data object, substantially in the form of a HTTP(S) POSTmessage including XML-formatted data, for example embodying a particularrequest for posting a group-based communication, as provided below:

POST /storage_message.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <storage_message> <message_identifier>ID_message_10</message_identifier> <team_identifier>ID_team_1</team_identifier> <channel_identifier>ID_channel_1</channel_identifier> <sending_user_identifier>ID_user_1</sending_user_identifier>  <topics> <topic>disclosures</topic>  <topic>patents</topic> <topic>policies</topic>  </topics>  <responses>  <response>liked byID_user_2</response>  <response>starred by ID_user_3</response> </responses>  <body contents>That is an interesting disclosure. I haveattached a copy our patent policy.</body contents> <attachments>patent_policy.pdf</attachments>  <conversation_primitive> conversation includes messages: ID_message_8, ID_message_9, ID_message_10, ID_message_11, ID_message_12  </conversation_primitive></storage_message>

In some embodiments, a sending user account identifier may be associatedwith the message communication. In one implementation, the message maybe parsed (e.g., using PHP—i.e., the script language derived fromPersonal Home Page Tools—commands) to determine a sending user accountidentifier of the user who sent the group-based communication.

In some embodiments, topics may be associated with the group-basedcommunication. In one implementation, the communication contents may beparsed (e.g., using PHP commands) to determine topics discussed in thegroup-based communication. For example, hashtags in the group-basedcommunication may indicate topics associated with the group-basedcommunication. In another example, the group-based communication may beanalyzed (e.g., by itself, with other group-based communications in aconversation primitive) or parsed using a machine learning technique,such as topic modeling, to determine topics associated with thegroup-based communication.

In some embodiments, data indicating responses may be associated withthe group-based communication. For example, responses to the group-basedcommunication by other users may include reactions (e.g., selection ofan emoji associated with the group-based communication, selection of a“like” button associated with the group-based communication), clickingon a hyperlink embedded in the group-based communication, replying tothe group-based communication (e.g., posting a group-based communicationto the group-based communication channel in response to thecommunication), downloading a file associated with the group-basedcommunication, sharing the group-based communication from onegroup-based communication channel to another group-based communicationchannel, pinning the group-based communication, starring the group-basedcommunication, and/or the like. In one implementation, data regardingresponses to the group-based communication by other users may beincluded with the group-based communication, and the group-basedcommunication may be parsed (e.g., using PHP commands) to determine theresponses. In another implementation, data regarding responses to thegroup-based communication may be retrieved from a database. For example,data regarding responses to the group-based communication may beretrieved via a MySQL database command similar to the following:

SELECT messageResponses FROM MSM_Message WHERE messageID =ID_message_10.

For example, data regarding responses to the group-based communicationmessage may be used to determine context for the group-basedcommunication (e.g., a social score for the group-based communicationfrom the perspective of some user). In another example, data regardingresponses to the group-based communication may be analyzed to determinecontext regarding the user (e.g., the user's expertise in a topic may bedetermined based on the responses to the user's group-basedcommunication regarding the topic).

In some embodiments, attachments may be included with the group-basedcommunication. If there are attachments, files may be associated withthe group-based communication. In one implementation, the group-basedcommunication may be parsed (e.g., using PHP commands) to determine filenames of the attachments. For example, file contents may be analyzed todetermine context for the group-based communication message (e.g., apatent policy document may indicate that the group-based communicationis associated with the topic “patents”).

In some embodiments, third-party metadata may be associated with thegroup-based communication. For example, third-party metadata may provideadditional context regarding the group-based communication message orthe user that is specific to a company, group, a group-basedcommunication workspace, a group-based communication channel, and/or thelike. In one implementation, the group-based communication message maybe parsed (e.g., using PHP commands) to determine third-party metadata.For example, third-party metadata may indicate whether the user who sentthe group-based communication is an authorized representative of thegroup-based communication channel (e.g., an authorized representativemay be authorized by the company to respond to questions in thegroup-based communication channel).

In some embodiments, a conversation primitive may be associated with thegroup-based communication. In one implementation, a conversationprimitive is an element used to analyze, index, store, and/or the likecommunications. For example, the group-based communication message maybe analyzed by itself, and may form its own conversation primitive. Inanother example, the group-based communication may be analyzed alongwith other group-based communication messages that make up aconversation, and the group-based communication messages that make upthe conversation may form a conversation primitive. In oneimplementation, the conversation primitive may be determined as thegroup-based communication message, a specified number (e.g., two) ofpreceding group-based communication messages and/or a specified number(e.g., two) of following group-based communication messages. In anotherimplementation, the conversation primitive may be determined based onanalysis of topics discussed in the group-based communication messageand other group-based communication messages (e.g., in the group-basedcommunication channel) and/or proximity (e.g., communication send orderproximity, communication send time proximity) of these group-basedcommunication messages.

In embodiments, various metadata, determined as described above, and/orthe contents of the group-based communication message may be used toindex the communication (e.g., using the conversation primitive) tofacilitate various facets of searching (i.e., search queries that returnresults from group-based communication datastore 102B). In at least oneexample implementation, a storage request data object may be sent fromgroup-based communication server 102A to facilitate indexing ingroup-based communication datastore 102B. In another implementation,metadata associated with the group-based communication may be determinedand the communication may be indexed in group-based communicationdatastore 102B. In an example embodiment, the group-based communicationmay be indexed such that a company's or a group's communications areindexed separately (e.g., in a separate index associated with the groupand/or company that is not shared with other groups and/or companies).In one implementation, group-based communications may be indexed at aseparate distributed repository (e.g., to facilitate data isolation forsecurity purposes).

If there are attachments associated with the group-based communication,file contents of the associated files may be used to index such files ingroup-based communication datastore 102B to facilitate searching. In atleast one embodiment, the files may be indexed such that a particularorganization's, company's or a group's files are indexed at a separatedistributed repository.

Example Apparatuses of the Present Disclosure

The group-based communication system 102 may be embodied by one or morecomputing systems, such as the apparatus 200 shown in FIG. 2 . Theapparatus 200 may include a processor 202, memory 204, input/outputmodule 206, communications module 208, group-based communication module210, and central channel management module 212. The apparatus 200 may beconfigured, using one or more of the modules to execute the operationsdescribed herein.

Although the components are described with respect to functionallimitations, it should be understood that the particular implementationsnecessarily include the use of particular hardware. It should also beunderstood that certain of the components described herein may includesimilar or common hardware. For example, two modules may both leverageuse of the same processor, network interface, storage medium, or thelike to perform their associated functions, such that duplicate hardwareis not required for each module. The use of the term “module” and/or theterm “circuitry” as used herein with respect to components of theapparatus 200 should therefore be understood to include particularhardware configured to perform the functions associated with theparticular module as described herein.

Additionally or alternatively, the terms “module” and “circuitry” shouldbe understood broadly to include hardware and, in some embodiments,software and/or firmware for configuring the hardware. For example, insome embodiments, “module” and “circuitry” may include processingcircuitry, storage media, network interfaces, input/output devices, andthe like. In some embodiments, other elements of the apparatus 200 mayprovide or supplement the functionality of the particular module. Forexample, the processor 202 may provide processing functionality, thememory 204 may provide storage functionality, the communications module208 may provide network interface functionality, and the like, to one ormore of the other modules.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus. The memory 204may be non-transitory and may include, for example, one or more volatileand/or non-volatile memories. In other words, for example, the memorymay be an electronic storage device (e.g., a computer readable storagemedium). The memory 204 may be configured to store information, data,content, applications, instructions, or the like, for enabling theapparatus 200 to carry out various functions in accordance with exampleembodiments of the present disclosure.

The processor 202 may be embodied in any one of a myriad of ways andmay, for example, include one or more processing devices configured toperform independently. Additionally or alternatively, the processor 202may include one or more processors configured in tandem via a bus toenable independent execution of instructions, pipelining, and/ormultithreading. The use of the terms “processor,” “processing module,”and “processing circuitry” may be understood to include a single-coreprocessor, a multi-core processor, multiple processors internal to theapparatus, other central processing unit (“CPU”), microprocessor,integrated circuit, and/or remote or “cloud” processors.

In an example embodiment, the processor 202 may be configured to executecomputer-coded instructions stored in the memory 204 or otherwiseaccessible to the processor. Alternatively, or additionally, theprocessor 202 may be configured to execute hard-coded functionality. Assuch, whether configured by hardware or software means, or by acombination thereof, the processor 202 may represent an entity (e.g.,physically embodied in circuitry) capable of performing operationsaccording to an embodiment of the present disclosure while configuredaccordingly. Alternatively, as another example, when the processor isembodied as an executor of software instructions, the instructions mayspecifically configure the processor to perform the algorithms and/oroperations described herein when the instructions are executed.

As one example context, the processor 202 may be configured to providegroup-based communication system functionality. Additionally oralternatively, the processor 202 may be configured to facilitate storingof data associated with group-based communication system functionality(e.g., organization data, workspace data, channel data, and/orgroup-based communication message data), and enable management of saidstored data in a centralized manner. For example, the processor 202 maybe configured to perform an authentication process and initiate anauthenticated session associated with a particular authenticated useraccount. Additionally or alternatively, the processor 202 may beconfigured to identify group-based communication channels permissionedfor management by the authenticated user account, for example where theauthenticated user account is an administrator user account based onstored administrator data, such as owner account data and/or delegatedaccount data. In yet some embodiments, the processor is furtherconfigured to identify particular information associated with eachidentified group-based communication channel, for example one or moreexternal resources available within the group-based communicationchannel, one or more authenticated user accounts, or groups ofauthenticated user accounts, having access to the group-basedcommunication channel, and/or other channel information based onmetadata associated with the group-based communication channel and/ordata transmitted within the group-based communication channel (e.g., oneor more group-based communication messages). The processor 202 mayadditionally or alternatively be configured to cause rendering ofgroup-based communication interfaces enabling functionality forcentralized channel management as described herein.

In some embodiments, the apparatus 200 includes input/output module 206that may, in turn, be in communication with processor 202 to provideoutput to the user and, in some embodiments, to receive an indication ofa user input. The input/output module 206 may comprise a user interface(e.g., a group-based communication interface) and may include a displayto which the user interface is rendered. In some embodiments, theinput/output module 206 may comprise a web user interface, a mobileapplication (e.g., a mobile group-based communication serviceapplication), a desktop application (e.g., a desktop group-basedcommunication service application), a linked or networked client device,a kiosk, or the like. In some embodiments, the input/output module 206may also include a keyboard, a mouse, a joystick, a touch screen, touchareas, soft keys, a microphone, a speaker, or other input/outputmechanisms. The processor and/or user interface module comprising theprocessor, for example processor 202, may be configured to control oneor more functions of one or more user interface elements throughcomputer program instructions (e.g., software and/or firmware) stored ona memory accessible to the processor (e.g., memory 204, and/or thelike). In some embodiments, the input/output module 206 comprises aclient device with which a user communicates with the apparatus 200.

The communications module 208 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the communications module 208may include, for example, at least a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications module 208 may include one or more networkinterface cards, antennas, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communication interface may include the circuitry for interactingwith the antenna(s) to cause transmission of signals via the antenna(s)or to handle receipt of signals received via the antenna(s).

The group-based communication module 210 includes hardware, software,firmware, and/or a combination thereof, configured to supportfunctionality associated with group-based communication system 102. Thegroup-based communication module 210 may utilize processing circuitry,such as the processor 202, to perform these actions. In someembodiments, the group-based communication module 210 includes hardware,software, firmware, or a combination thereof, to process group-basedcommunication messages posted by one or more authenticated useraccount(s) to various group-based communication channels, and/or postedby one or more external resource(s) to various group-based communicationchannel(s), transmit corresponding information to one or more clientdevice(s) and/or external resources for processing. For example, in thisregard, the group-based communication module 210 may providefunctionality to enable the apparatus 200 to function as an intermediaryservice between the various users associated with disparate clientdevices, and the various users and external resources providingsupplemental functionality built over the group-based communicationsystem. In some embodiments, the group-based communication module 210may additionally and/or alternatively be configured to send data and/orreceive data from one or more group-based communication datastore(s),for example datastore 102B. In some implementations, the sent and/orreceived data may be data objects embodying one or more group-basedcommunications (e.g., messages, files, links, etc.) organized among aplurality of group-based communication channels. Additionally oralternatively, the group-based communication module 210 may providefunctionality for authenticating authentication credentials to initiatean authenticated session associated with a corresponding client device.During the authenticated session, the apparatus 200, for example via thegroup-based communication module 210 may provide native communicationfunctionality and/or functionality associated with the externalresources. It should be appreciated that, in some embodiments, thegroup-based communication module 210 may include a separate processor,specially configured field programmable gate array (FPGA), or aspecially configured application-specific integrated circuit (ASIC).

The central channel management module 212 includes hardware, software,firmware, and/or a combination thereof, configured to supportfunctionality associated with management of one or more entities withinthe group-based communication system, for example centralized channelmanagement via the apparatus 200. In at least one example embodiment,the central channel management module 212 is configured via hardware,software, firmware, or a combination thereof, to receive a channelmanagement request associated with one or more group-based communicationchannels. In some embodiments, the channel management request includesor is otherwise associated with an authenticated user account identifierfor the authenticated user account that originated the request.Additionally or alternatively, in some example embodiments, thecentralized channel management module is configured to process one ormore received channel management requests, for example to identifyrequested data associated with one or more group-based communicationchannels configured for management by the identified authenticated useraccount and provide such requested data as a response to the request, orto execute one or more data management operations (e.g., granting newpermission data for management and/or access of a channel, revokingpermission data for management and/or access of a channel, deletingand/or editing group-based communication messages stored within agroup-based communication channel, removing and/or adding connectionswith one or more external resources within a group-based communicationchannel, and/or the like), and providing a response to the request basedon whether processing was determined successful. The channel managementrequest(s) may be associated with an identified group-basedcommunication channel set, for example by including a plurality ofchannel identifiers associated with group-based communication channelsto be managed. Alternatively or additionally, the channel managementrequest(s) may be include data for use in identifying a group-basedcommunication channel set for management, for example a group-basedcommunication channel type for use in identifying all group-basedcommunication channels of the group-based communication type that aremanageable by the authenticated user account.

Additionally or alternatively, in some embodiments, the central channelmanagement module 212 includes software, hardware, firmware, and/or acombination thereof, for enabling rendering of a centralized channelmanagement dashboard. For example, the central channel management module212 may be configured to cause rendering of a centralized channelmanagement dashboard upon request by a user via a client device, forexample by receiving. In some such embodiments, the centralized channelmanagement request may include, or otherwise be associated with, anauthenticated user account identifier that submitted or otherwiseoriginated the request, for example for use in identifying thegroup-based communication channels that the authenticated user accountis permissioned to manage. Additionally or alternatively, in someembodiments, the central channel management module 212 includeshardware, software, firmware, or a combination thereof, to identify datafor use in causing rendering of the centralized channel managementdashboard, for example a group-based communication channel metadata setfor the group-based communication channels permissioned for managementby the authenticated user account. In some embodiments, the centralchannel management module 212 additionally or alternative includeshardware, software, firmware, and/or a combination thereof, tocommunicate with one or more datastores for processing receivedrequests, for example to communicate with one or more datastores storinggroup-based communication channel metadata and/or content data, forexample to initiate one or more data queries, and/or to receive andparse response data associated with the data queries.

In some embodiments, the central channel management module 212, alone orin conjunction with one or more other modules such as the processor 202and/or input/output module 206, include hardware, software, and/or acombination thereof, configured to generate one or more interfacesincluding specially configured interface elements for initiating and/orotherwise causing such operations described above, and/or providing suchinterfaces for interaction by one or more users, such as throughcommunication with one or more client device(s), displays, and/or thelike. It should be appreciated that, in some embodiments, the centralchannel management module 212 may include a separate processor,specially configured FPGA, or a specially configured ASIC.

In some embodiments, one or more of the aforementioned components iscombined to form a single module. For example, in some embodiments, thegroup-based communication module 210 and/or central channel managementmodule 212, and/or processor 202, are combined into a single module. Thecombined module may be configured to perform some or all of thefunctionality described above with respect to the individual modules.Additionally or alternatively, in some embodiments, one or more of themodules described above may be configured to perform one or more of theactions described with respect to one or more of the other modules.

One of the client devices 104 may be embodied by one or more userdevices, such as the apparatus 300 shown in FIG. 3 . The apparatus 300may include a processor 302, memory 304, input/output module 306,communications module 308, and group-based client module 310. Theapparatus 300 may be configured, using one or more of the modules toexecute the operations described herein. The components 302-308 mayfunction similar or identical to the similarly named components depictedand described above with respect to apparatus 200. For purposes ofbrevity, repeated disclosure with regard to the functionality of suchsimilarly named components is omitted.

The group-based client module 310 includes hardware, software, firmware,and/or a combination thereof, configured to support functionalityassociated with accessing and utilizing a group-based communicationsystem. In this regard, in some embodiments, the group-based clientmodule 310 is configured to enable a user to initiate an authenticatedsession associated with an authenticated user account, for example byinputting user authentication credentials for authenticating via agroup-based communication system. Additionally or alternatively, in someembodiments, the group-based client module 310 is configured to transmitone or more requests for identifying channel information for manageablegroup-based communication channels and/or to transmit one or morerequests for performing one or more actions for managing the group-basedcommunication channels. In some embodiments, the group-based clientmodule 310 additionally or alternatively includes software, hardware,firmware, or a combination thereof, for receiving one or moreresponse(s) to the one or more transmitted request(s), and/or processingthe received responses. It should be appreciated that, in someembodiments, the group-based client module 310 may include a separateprocessor, specially configured FPGA, or a specially configured ASIC.

In some embodiments, one or more of the aforementioned components ofapparatus 300 is combined to form a single module. For example, in someembodiments, the group-based client module 310 is combined with one ormore other modules into a single module, for example in combination withprocessor 302. The combined module may be configured to perform some orall of the functionality described above with respect to the individualmodules. Additionally or alternatively, in some embodiments, one or moreof the modules described above may be configured to perform one or moreof the actions described with respect to one or more of the othermodules.

Example Group-Based Computing Environment

FIGS. 4A and 4B depict an example computing environment representingaspects of a group-based communication system, in accordance with atleast one example embodiment of the present disclosure. The examplecomputing environment includes a plurality of entities managed withinthe computing environment, specifically organizations, workspaces,channels, and message sets, arranged according to an entity hierarchy.Specifically, the example computing environment includes an organization402, group-based workspaces 404A-404D (collectively “workspaces 404”),group-based communication channels 406A-406C (collectively “channels406”), group-based communication channels 408A-408B (collectively“channels 408”), group-based communication channel 410, and group-basedcommunication channels 412A-412B (collectively “channels 412”), andmessage sets 414A-414F (collectively “message sets 414”). In someembodiments, the computing environment may be maintained via hardware,software, firmware, or a combination thereof, of one or more computingsystems, for example a group-based communication system embodied by theapparatus 200.

Within an example computing environment, an organization may beassociated with any number of workspaces. For example as illustrated,the organization 402 is associated with each of the workspaces 404. Insome embodiments, the workspaces 404 are separated based on intendeduser groups and/or use cases. As such, in some embodiments, each of theworkspaces 404 is associated with permission data configured to enablecertain authenticated user accounts to access each workspace. In thismanner, the computing environment provides requisite security measuresto ensure that only allowed user authenticated user accounts may accesseach of the workspaces 404.

Further, in at least some embodiments, each of the workspaces may beassociated with any number of channels. For example as illustrated,workspace 404A is associated with, and/or otherwise includes channels406, workspace 404B includes channels 408, workspace 404C includeschannel 410, and workspace 404D includes channels 412. The channels mayeach be configured to embody a group-based communication channel havingany channel type, for example may be a private group-based communicationchannel or a public group-based communication channel. Additionally oralternatively, each channel may be configurable as a common group-basedcommunication channel to be shared with another entity, for exampleshared with another organization via another workspace or with anotherworkspace maintained by the same organization 402. Further, in someembodiments, one or more group-based communication channels isconfigurable such that only a subset of the authenticated user accountspermissioned for accessing the channel are further permissioned toaccess the channel. It should be appreciated that in some contexts, aworkspace may include a plurality of channels of a certain channel type.For example, channel 406A and channel 406C may each embody publicgroup-based communication channels, while channel 406 may embody aprivate group-based communication channel. Any of such group-basedcommunication channels may be shared for configuring as a commongroup-based communication channel with at least one other entity.

Further, in at least some embodiments, each of the channels isassociated with a group-based communication message set. The group-basedcommunication message set may include group-based communication messagesposted to the channel by authenticated user accounts having access tothe channel, and/or external resources associated with the channel. Forexample, the message set 414A corresponds to any number of group-basedcommunication messages posted within channel 406A. Similarly, messageset 414B corresponds to any number of group-based communication messagesposted within channel 406B, and so on. Group-based communicationmessages may be posted by users using one or more client devices, forexample to be stored and transmitted to one or more other user devicesassociated with other authenticated user accounts accessing thegroup-based communication channel. In this regard, a user may select agroup-based communication channel, for example within a group-basedcommunication interface, to enable posting of the group-basedcommunication message to the selected group-based communication channel.Additionally or alternatively, an external resource may transmit agroup-based communication message in response to user request, forexample embodied by another group-based communication message within thegroup-based communication channel, or automatically, for example inresponse to one or more events determined by the external resource or anassociated external system. In some embodiments, an external resource isconfigured to communicate with a group-based communication system viaone or more APIs.

FIG. 4B illustrates a hierarchy of user accounts associated with anorganization, in accordance with at least one embodiment of the presentdisclosure. As illustrated, an organization may be associated with, orotherwise “include,” any number of user accounts. The user accounts mayeach be associated with any number of users, for example in at least onecontext each user account is associated with one user, in other contextsa user account is associated with any number of users and/or each useris associated with any number of user accounts. As illustrated, theorganization 402 is associated with authenticated u4ser accounts450A-450N (collectively “authenticated user accounts 450”). In at leastsome embodiments, each of the authenticated user accounts 450 isassociated with different administrator permission data, for examplesuch that the functionality available to each of the authenticated useraccounts 450 differs with respect to managing various group-basedcommunication channels, and/or other entities, associated with theorganization 402. As illustrated for example, the user account 450A andthe user account 450B each embody an administrator user account for theorganization 402. In this regard, the administrator user accounts mayeach be permissioned for managing data associated with the organization402, and/or other entities associated therewith. For example in at leastsome embodiments, each of the administrator user accounts 450A and 450Bare permissioned for managing any of the group-based communicationchannels for group-based workspaces associated with the organization402. With respect to the entities depicted in FIG. 4A, for example, theadministrator user accounts 450A and 450B may each be configured tomanage settings, data, and/or other information associated with each ofthe channels 406, 408, 410, and/or 412, and/or to manage the messagesets 414 associated with any of such channels.

Additionally or alternatively, the administrator user accounts 450A and450B may each designate one or more other user accounts as administratoruser accounts with respect to the organization 402, and/or one or moresub-entities associated with the organization 402. It should beappreciated that, in some embodiments, any authenticated user accountmay be designated as an administrator user account for one or moreentities, and that different authenticated user accounts may bedesignated as authenticated user accounts with respect to varioussub-entities associated with the organization 402. In this regard, theuser accounts designated as administrator user accounts for one or moreentities may be associated with permission data indicating the useraccount may manage the one or more entities. Additionally oralternatively, in some embodiments, the group-based communication systemis configured to enable an administrator user account for a particularentity to designate one or more other authenticated user accounts havingaccess to the entity as administrator user account(s) for the entityand/or sub-entities thereof.

In at least one example context, the administrator user account 450A maydesignate the authenticated user account 450D as an administrator ofworkspace 404A, for example causing storing of permission dataindicating the authenticated user account 450D is permissioned to managedata associated with the workspace 404A and/or the sub-entities thereofincluding the channel set 406 and/or message sets 414A-414C. In thisregard, the group-based communication system may be configured todetermine, based on the permission data, that the workspace 404A andsub-entities thereof are the each manageable by the authenticated useraccount 450D. In some such embodiments, managing a workspace may includealtering one or more settings and/or parameter values associated withthe workspace, deleting sub-entities thereof (e.g., deleting a channelfrom the channel set 406), and/or adding a sub-entity (e.g., adding achannel to the channel set 406).

Additionally or alternatively, the administrator user account 450 maydesignate the authenticated user account 450D as an administrator of agroup-based communication channel, for example of group-basedcommunication channel 408A. In this regard, the authenticated useraccount 450D may be associated with permission data indicating theauthenticated user account 450D is permissioned to manage dataassociated with the channel 408A and/or sub-entities thereof includingthe message set 414D. In such contexts, the authenticated user account450D is permissioned to manage the channel 408A, but is not permissionedfor managing sister-entities (such as the channel 408B and/or othergroup-based communication channels in the channel set 408) or anyhigher-level entities such as the workspace 404B. In this regard, thegroup-based communication system may be configured to determine, basedon the permission data, that the channel 408A and sub-entities thereofare the only entities manageable by the authenticated user account 450D.

Example Centralized Channel Management Information and Interfaces

FIGS. 5A, 5B, 5C, 6A, 6B, and 7-8 illustrate example user interfacesincluding various information and enabling various functionality forcentralized channel management, in accordance with at least one exampleembodiment of the present disclosure. It should be appreciated that theinformation depicted in the various user data is exemplary, and thatsimilar and/or alternative data, parameters, data values, and/or thelike may be provided. Additionally or alternatively, in someembodiments, the layout of the various interface elements, and/orsub-interfaces of each depicted user interface may differ withoutdeviating from scope of this disclosure. Further, it should beappreciated that, in some embodiments, data and/or information forcentralized channel management may be provided without one or morecorresponding user interfaces, for example via one or more APIs madeavailable via a group-based communication system. As such, the exampledepicted interfaces, sub-interfaces, elements, and data values depictedtherein are provided for descriptive and illustrate purposes and are notto limit the scope or spirit of the disclosure herein.

FIG. 5A illustrates an example centralized channel management dashboard500 (“dashboard 500”), in accordance with at least one exampleembodiment of the present disclosure. The dashboard 500 may be renderedto a client device associated with an authenticated user account, forexample, during an authenticated session. In some embodiments, agroup-based communication system causes rendering of the dashboard 500via the client device, for example by transmitting data to be used inconfiguring and/or populating the dashboard 500, and/or transmittingdata embodying the dashboard 500, to the client device. In someembodiments, the group-based communication system causes rendering ofthe dashboard 500 to the client device in response to one or morerequests to access the dashboard transmitted from the client device tothe group-based communication system.

As illustrated, the dashboard 500 includes a plurality of data columnsrepresenting different channel data values for a plurality ofgroup-based communication channels. Specifically, the dashboard 500includes data associated with a manageable group-based communicationchannel set 504. The manageable group-based communication channel set504 may be associated with a particular authenticated user account, forexample such that the authenticated user account is permissioned tomanage each channel in the manageable group-based communication channelset 504. In this regard, the authenticated user account may beassociated with permission data for one or more channel(s) in themanageable group-based communication channel set 504, and/or with one ormore higher-level entities (e.g., a workspace or organization)associated with one or more channel(s) in the manageable group-basedcommunication channel set. In this regard, it should be appreciated thatin at least some such embodiments, the dashboard 500 is customized basedon information identified as manageable by the authenticated useraccount accessing the dashboard 500.

The dashboard 500 includes information associated with a number ofgroup-based communication channels manageable by a particularauthenticated user account, specifically identified as manageablegroup-based communication channel set 504. The manageable group-basedcommunication channel set 504 may include any number of group-basedcommunication channels of various types. For example, in someembodiments, an authenticated user account is permissioned for managinga group-based communication channel and/or managing access to thegroup-based communication channel directly, or indirectly based onpermission data for one or more higher-level entities. Additionally oralternatively, in some embodiments, an authenticated user account may beassociated with permission data for managing a group-based communicationchannel for which the authenticated user account is not a member (e.g.,an inaccessible group-based communication channel). For example, anadministrator user account with respect to a group-based communicationchannel may delegate permission data for managing a private group-basedcommunication channel to another authenticated user account that has notjoined the private group-based communication channel. In this regard, itshould be appreciated that an authenticated user account does not needto be a member of an entity to be permissioned for managing the entity(e.g., an authenticated user account may manage an organization,workspace, and/or channel inaccessible to the authenticated useraccount). In some such embodiments, the dashboard 500 neverthelessincludes one or more inaccessible group-based communication channel(s)in the manageable group-based communication channel set 504. Forexample, in this regard, a particular authenticated user account may bepermissioned for managing one or more workspace(s) and/or group-basedcommunication channels(s), for example, that the user is notpermissioned to access, for example for purposes of posting newmessages, receiving messages, and/or otherwise interacting within theentity.

Each row of the manageable group-based communication channel set 504comprises data values for various parameters of a group-basedcommunication channel, and/or associated with the group-basedcommunication channel, manageable by the authenticated user account.Each data column may include a data value associated with a parameterfor the channel. It should be appreciated that the dashboard 500 may beconfigured to include any parameter of and/or associated with agroup-based communication channel, and such parameters are not limitedto the exemplary parameters depicted in FIG. 5 . In an example context,as illustrated, channel name column 504A includes a data value for aparameter representing a channel name for a group-based communicationchannel. In this regard, in at least some embodiments, interaction withthe channel name column 504A may cause the dashboard 500 and/or anassociated interface to be rendered for viewing and/or altering the datavalue representing the name of the group-based communication channelassociated with the row. Additionally or alternatively, as illustrated,workspace sharing column 504B includes a data value for a parameterrepresenting the number of workspaces with which a channel is shared. Inthis regard, interaction with the workspace sharing column 504B maycause the dashboard 500 and/or an associated interface to be renderedwith data for some or all of the workspaces with which the channel isshared, and/or may enable adjustment of the workspaces with which thechannel is shared (e.g., to share the channel in another workspace, orto remove sharing from an existing workspace). Additionally oralternatively, as illustrated, external sharing column 504C includesdata values for a parameter representing any third-party organizationswith which the channel is shared. In this regard, the external sharingcolumn 504C may include an identifier and/or other informationassociated with each third-party organization (other than the ownerorganization) with which the channel has been shared. Accordingly, achannel having data values indicating the channel was shared with atleast one third-party organization may embody a common group-basedcommunication channel for communicating between one or moreauthenticated user accounts for each organization. Additionally oralternatively, as illustrated, the member user column 504D includes adata value for a parameter representing the number of authenticated useraccounts having access to the channel. The data value may represent thenumber of authenticated user accounts having access to the channel fromany workspace and/or associated with any organization (including one ormore third-party organizations in a circumstance where the channel isshared). It should be appreciated that a centralized channel managementdashboard, for example the dashboard 500, may be configured to includeany of various types of information. For example, in at least someexample embodiments, the dashboard may be configured to include one ormore of channel creation timestamp data, channel creator account data,historical activity data, channel share status data, channel gueststatus data, and/or any combination thereof.

In some embodiments, user interaction with one or more of the rows ofthe manageable group-based communication channel set 504 causesrendering of another interface, or sub-interface, based on thecorresponding group-based communication channel of the manageablegroup-based communication channel set 504. For example, in at least oneexample context, user interaction may cause rendering of a member listfor the group-based communication channel (e.g., all authenticated useraccounts and/or guest user accounts). In yet other embodiments, userinteraction causes rendering of another interface, or sub-interface,providing more information based on the data value with which the userinteraction occurred. For example, in a circumstance where the userinteracts with a data value of the workspace sharing column 504B, aninterface and/or sub-interface may be rendered that includes informationassociated with the workspaces having access to the group-basedcommunication channel (e.g., names of such workspaces, and/or the like).For example, in some such embodiments, one or more of the interfacesdescribed below with respect to FIGS. 5B, 5C, 6A and/or 6B are accessedin response to such user interaction.

Additionally or alternatively, in some embodiments, the rows associatedwith the manageable group-based communication channel set 504 may besorted within the dashboard 500. For example, in at least someembodiments, a sub-interface associated with the data columns 504A-504Dis configured to receive user interaction indicating a desire to sortthe rows based on the data column. It should be appreciated that therows may be sorted in any of a myriad of manners for one or more datacolumns (e.g., alphabetically, reverse-alphabetically, descending order,ascending order, and/or the like).

It should be appreciated that the manageable group-based communicationchannel set 504 may include any number of group-based communicationchannels manageable by the authenticated user account. Accordingly, thedashboard 500 may include any number of rows corresponding to thechannels in the manageable group-based communication channel set 504.The dashboard 500 further include channel filtering element 508. Thechannel filtering element 508 may enable selection of one or morechannel parameter values to limit the rendered rows of the dashboard 500to include only the channels of the manageable group-based communicationchannel set 504 that meet the selected channel parameter values, oralternatively do not meet one or more of the selected channel parametervalues. For example, the channel parameter values may include values fora channel type, whether the channel is shared between one or moreworkspaces, whether the channel is shared with one or more third-partyorganizations, and/or the like.

Additionally or alternatively, the dashboard 500 may include channelsearch element 506 for limiting the rendered rows of the dashboard 500to include only the channels matching the value input into the channelsearch element 506. In this regard, the dashboard 500 may be rendered toinclude the one or more parameter values that include the value input tothe channel search element 506. It should be appreciated that in someembodiments filtering the dashboard 500 via the channel search element506 and the channel filtering element 508 may be combined.

Further, as illustrated, the dashboard 500 includes channel selectionelements 510, each channel selection element of the channel selectionelements 510 associated with a row representing a group-basedcommunication channel of the manageable group-based communicationchannel set 504. In this regard, interaction with a channel selectionelement of the channel selection elements 510 may select the row andcorresponding channel, for example to perform one or more channelmanagement actions. As such, interaction with a subset of the channelselection elements 510 enables selection of a subset of the manageablegroup-based communication channel set 504 such that a single channelmanagement action may be performed for the subset of channels in themanageable group-based communication channel set 504. Accordingly, auser may interact with the channel selection elements for selecting aparticular desired subset of group-based communication channels formanaging. In some embodiments, for example as illustrated, the channelselection elements 510 includes at least one channel selection elementspecially configuring for selecting, and/or deselecting, all channelsassociated with a row currently rendered via the dashboard 500. In thisregard, the user may interact with the channel selection elements 510 toselect a desired subset of the manageable group-based communicationchannel set 504 to be managed together according to one or moreuser-initiated channel management actions.

Additionally or alternatively, as illustrated, the dashboard 500 mayinclude a dashboard navigation sub-interface 502. The dashboardnavigation sub-interface 502 may include one or more interface elementsconfigured to receive user interaction, and subsequently alter theinformation rendered to the dashboard 500 based on the user interaction,and/or cause rendering of one or more associated interfaces foraccessing such associated interfaces. For example, in some embodiments,the dashboard navigation sub-interface 502 is configured to include oneor more interface elements for each workspace of an organization withwhich the authenticated user account is associated. Additionally oralternatively still, the dashboard navigation sub-interface 502 mayinclude interface elements for selecting a specific subset of themanageable group-based communication channel set 504 to be rendered viathe dashboard 500.

In some embodiments, the dashboard navigation sub-interface 502 mayinclude one or more interface elements configured to enable access toone or more interfaces providing functionality for altering dataassociated with organization-level channel management. In this regard,FIG. 5B illustrates an example dashboard sub-interface for alteringpermission data associated with organization-level channel management inaccordance with at least some example embodiments of the presentdisclosure. For example, as illustrated, the dashboard navigationsub-interface 502 includes an interface element (such as a button)titled “channel administration” for accessing the organization-levelchannel management interface 520.

The organization-level channel management interface 520 may include anynumber of interface elements for providing functionality associated withsetting organization defaults for managing sub-entities associatedthereof. It should be appreciated that, in some embodiments, theorganization-level channel management interface 520 includes any of amyriad of interface elements associated with setting managementpermissions for any number of such sub-entities.

As illustrated, for example the organization-level channel managementinterface 520 includes a public channel permission interface 522associated with a particular organization. In this regard, the publicchannel permission interface 522 may provide functionality for settingpermission data associated with managing public group-basedcommunication channels associated with the organization (for example,public group-based communication channels designated a defaultgroup-based communication channel for inclusion in all workspacesassociated with the organization, and/or public group-basedcommunication channels in any workspace associated with theorganization). As illustrated, the associated permission data indicatesonly the organization primary owners are permissioned for managingpublic group-based communication channels for the organization. Thepublic channel permission interface 522 further includes at least oneinterface element for editing the associated permission data, forexample via one or more further interfaces for selecting one or moreauthenticated user accounts, or groups of authenticated user accounts(e.g., “organization primary owners”) permissioned for managing thepublic group-based communication channel(s).

FIG. 5C illustrates an example interface for editing permission dataassociated with group-based communication channel management,specifically for editing permission data associated with managinggroup-based communication channels of a particular organization, inaccordance with at least some embodiments of the present disclosure. Inthis regard, FIG. 5C depicts an example permission editing interface550. The permission editing interface 550 may include one or moreinterface elements for editing permission data associated with managingpublic group-based communication channel(s) for an organization.

As illustrated, the permission editing interface 550 includes a userrole selection interface 552. The user role selection interface mayinclude one or more user roles for an authenticated user account. Inthis regard, each of the of the user roles may correspond to a differentlevel of administrative permissions associated with the organization. Inthis regard, a “primary owner” may be associated with an authenticateduser account for a top administrator in the organization. Similarly,“organization owner” may be delegated from the primary owner and/orotherwise preconfigured for one or more administrator authenticated useraccounts associated with the organization. Admin authenticated useraccounts associated with the role of “organization owner” may beassociated with the same permissions as the “primary owner,” however insome embodiments are not configured to alter the permissions of at leastthe primary owner. Further, “admin” may be delegated from the primaryowner and/or other organization owners, and may be associated with lesspermissions than the primary owner and/or organization owners, and/orthe same permissions, but are not configured to alter the managementpermissions for the organization owners and/or primary owner. It shouldbe appreciated that selecting one of the user roles, for example via oneor more interface elements associated with each role (such as the radiobuttons as depicted), corresponds to a set of authenticated useraccounts associated with the selected user role. In this regard, theassociated set of authenticated user accounts are to be permissioned formanaging the associated group-based communication channels (such aspublic group-based communication channels) upon submitting theselections via one or more interface elements (such as the “save” buttonas depicted).

The permission editing interface 550 further includes a user selectioninterface 554. The user selection interface 554 includes one or moreinterface elements for adding particular authenticated user account(s)to be permissioned for managing the associated group-based communicationchannels (such as public group-based communication channels asillustrated). In this regard, a user may input and/or select one or moreauthenticated user accounts, for example from a determined set of allauthenticated user accounts associated with the organization, forpermissioning. Upon submitting changes associated with the interface550, for example via the “save” button as depicted, the authenticateduser accounts specifically identified via the user selection interface554 may additionally or alternatively be permissioned for managing theassociated group-based communication channels (for example, publicgroup-based communication channels as depicted). It should beappreciated that any number of authenticated user accounts may beselected via the user selection interface 554.

Additionally or alternatively, as illustrated, for example theorganization-level channel management interface 520 includes a privatechannel permission interface 524 associated with a particularorganization. In this regard, the private channel permission interfaceelement 524 may provide functionality for setting permission dataassociated with managing private group-based communication channelsassociated with the organization (for example, private group-basedcommunication channels configured as a default group-based communicationchannel for includes in all workspaces associated with the organization,and/or private group-based communication channels in any workspaceassociated with the organization). As illustrated, the associatedpermission data indicates only the organization primary owners arepermissioned for managing private group-based communication channels forthe organization. The private channel permission interface 524 furtherincludes at least one interface element for editing the associatedpermission data, for example via one or more further interfaces forselecting one or more authenticated user accounts, or groups ofauthenticated user accounts (e.g., “organization primary owners”)permissioned for managing the private group-based communicationchannel(s). It should be appreciated that, in at least some embodiments,the interface element enables access to an interface similar orequivalent to that of permission editing interface 550 for settingpermission data associated with private group-based communicationchannels.

Additionally or alternatively, as illustrated, for example theorganization-level channel management interface 520 includesmulti-workspace channel permission interface 526 associated with aparticular organization. In this regard, the multi-workspace channelpermission interface 526 may provide functionality for settingpermission data associated with managing group-based communicationchannels accessible by a plurality of workspaces associated with theowner organization, and/or in some embodiments group-based communicationchannels accessible by at least one workspace associated with athird-party organization associated with the organization (for example,a group-based communication channel that the owner organization hasshared). As illustrated, the associated permission data indicates thatall non-guest authenticated user accounts are permissioned for creating,editing, and/or archiving group-based communication channels accessiblewithin a plurality of workspaces. The multi-workspace channel permissioninterface 526 further includes at least one interface element forediting the associated permission data, for example via one or morefurther interfaces for selecting one or more authenticated useraccounts, or groups of authenticated user accounts (e.g., “organizationprimary owners”) permissioned for managing group-based communicationchannel(s) accessible within a plurality of workspaces. It should beappreciated that, in at least some embodiments, the interface elementenables access to an interface similar or equivalent to that ofpermission editing interface 550 for setting permission data associatedwith multi-workspace group-based communication channels.

Additionally or alternatively, as illustrated, for example theorganization-level channel management interface 520 includes a sharedchannel request permission interface 528 associated with a particularorganization. In this regard, the shared channel request permissioninterface 528 may provide functionality for setting permission dataassociated with enabling authenticated user accounts to submit requeststo share a group-based communication channel, and/or permission dataassociated with enabling approval and/or rejection of submitted requeststo share a group-based communication channel. As illustrated, theassociated permission data indicates that shared channel request(s) maybe submitted and only the organization primary owners and organizationadmins (e.g., delegated administrator authenticated user accountsassociated with the organization) are permissioned for approving and/orrejecting the shared channel request. The shared channel requestpermission interface 528 further includes at least one interface elementfor editing the associated permission data, for example via one or morefurther interfaces for selecting one or more authenticated useraccounts, or groups of authenticated user accounts (e.g., “organizationprimary owners” and/or “organization administrators,” and/or acombination thereof) permissioned for approving and/or rejecting sharedchannel requests in circumstances where such requests are enabled. Itshould be appreciated that, in at least some embodiments, the interfaceelement enables access to an interface similar or equivalent to that ofpermission editing interface 550 for setting permission data associatedwith shared channel requesting and/or approval.

In some embodiments, one or more additional interface elements areprovided that enable organization-level channel management. For example,in at least one embodiment, one or more interface elements are providedfor editing management permission for which authenticated user accountsare permissioned to invite to private group-based communicationchannels, and separate one or more interfaces for editing managementpermission for which authenticated user accounts are permissioned forsetting group-based communication channels as private and/or public. Inthis regard, it should be appreciated that an organization may beassociated with various permission data associated with variousfunctionality to be performed via the group-based communication system.Similarly, it should be appreciated that each such permission data maybe associated with one or more separate sets of interface element(s)such that permission data may be set to one or more desired valuesindividually. Alternatively or additionally, in some embodiments, one ormore portions of permission data may correspond to a plurality offunctionality, for example where a single setting corresponds topermission to invite to a private group-based communication channel andset a group-based communication channel as either private or public.

Additionally or alternatively, as illustrated, the organization-levelchannel management interface 520 may include one or more additionalinterface elements for configuring one or more group-based communicationchannels as a default group-based communication channel for theorganization. In this regard, in at least one example embodiment, eachdefault group-based communication channels may be accessible from withineach workspace associated with the organization. In this regard, theorganization-level channel management interface 520 may include aninterface element associated with each group-based communication channelcurrently configured as a default group-based communication channel,and/or one or more interface elements for editing such configurationsand/or configuring the group-based communication channel to remove it asa default group-based communication channel. Additionally oralternatively still, the organization-level channel management interface520 may include an interface element associated with configuring one ormore group-based communication channel(s) as a default group-basedcommunication channel, for example where such group-based communicationchannel(s) are currently not configured as a default group-basedcommunication channel for the organization.

FIG. 6A illustrates an example interface of a centralized channelmanagement dashboard 600 (“interface 600”), in accordance with at leastone example embodiment of the present disclosure. In at least oneembodiment, the interface 600 embodies a centralized channel managementdashboard, or sub-interface thereof, for example to enable initiation ofone or more channel management action(s) associated with at least onechannel. In this regard, the interface 600 may enable initiation of achannel management action for one selected channel (e.g., based on theinterface element interacted with by the user) or for a plurality ofselected channels (e.g., based on interaction with one or more channelselection elements of a dashboard).

The interface 600 includes channel management interface element 602. Insome embodiments, a channel management interface element 602 is renderedfor each row within the interface 600 associated with a manageablegroup-based communication channel. In this regard, interaction with thechannel management interface element 602 may be associated withaccessing interface elements for initiating channel management actionsperformable for the corresponding group-based communication channel. Inthis regard, interaction with the channel management interface element602 may cause rendering of a management action options interface 604.The management action options interface 604 includes a set of interfaceelements, each associated with initiating a different channel managementaction for at least the channel associated with the channel managementinterface element 602 with which the user interacted. As illustrated,the management action options interface 604 includes a first interfaceelement for managing members of the channel, a second interface elementfor managing settings for the channel, and a third interface element forarchiving the channel. It should be appreciated that, in someembodiments, user interaction with one or more of the interface elementsof the management action options interface 604 causes initiation of thenassociated channel management actions via the group-based communicationsystem.

Additionally or alternatively, in some embodiments, the managementaction options interface 604 is configured to initiate one or morechannel management actions for a selected set of channels. For example,interaction with the an interface element of the management actionoptions interface 604 may initiate the channel management action foreach of the selected group-based communication interfaces. In thisregard, the selected group-based communication channels may be managedwith reduced interactions, such that each group-based communicationchannel is not required to be managed individually.

FIG. 6B illustrates an example interface for centralized channelmanagement, specifically for channel member management, in accordancewith at least one example embodiment of the present disclosure.Specifically, FIG. 6B depicts channel member management interface 650.The channel member management interface 650 includes a plurality ofinformation associated with a selected channel, for example the channel“#engineering” as illustrated. In some embodiments, the channel membermanagement interface 650 is accessed based on user interaction with oneor more elements of the dashboard 500, and/or interface 600, such asuser interaction with an interface element associated rendered to thedashboard associated with a selected group-based communication channel.For example, in at least one context, the channel member managementinterface 650 is accessed in response to user interaction with the#engineering interface element rendered to the dashboard 500, or acorresponding channel management interface element 602 as depicted anddescribed with respect to FIG. 6A. Additionally or alternatively, thechannel member management interface 650 may be accessed via thedashboard navigation sub-interface 502.

The channel member list 652 includes an interface element associatedwith each authenticated user account permissioned to access the selectedgroup-based communication channel. In this regard, the channel memberlist 652 may include one or more associated data values for theauthenticated user account, such as an associated account name, and/oraccount email and/or identifier. Additionally or alternatively, in atleast some embodiments, the channel member list 652 includes an elementindicating whether the authenticated user account is associated withfull access permissions, and/or limited access permissions (e.g., as aguest account, and/or an authenticated user account associated with athird-party organization). Additionally or alternatively still, in atleast some embodiments, each authenticated user account is associatedwith one or more interface elements for editing the access and/ormanagement permission data associated with the authenticated useraccount. For example, a button may be provided together with eachauthenticated user account to remove access permissions for theauthenticated user account, limiting access permissions for theauthenticated user account, granting access permissions for theauthenticated user account, and/or the like. In some embodiments, thechannel member list 652 is determined based on all authenticated useraccounts for one or more workspaces (for example, in the circumstancewhere the channel is public) and/or a configured authenticated accountdata set indicating authenticated user accounts associated with thegroup-based communication channel, the authenticated account data setindicating authenticated user account(s) that were invited, andaccepted, access to the selected group-based communication channeland/or otherwise permissioned for accessing the selected group-basedcommunication channel (for example, in a circumstance where the channelis private). In some embodiments, the channel member managementinterface 650 includes one or more sorting, searching, and/or filteringinterface elements for altering the authenticated user accounts renderedto the channel member list 652 based on any data parameter embodying theauthenticated user account (e.g., identifier, name, display name,alternative name, email, role, and/or the like).

The channel member management interface 650 further includes memberadding element 654. In some embodiments, the member adding element 654enables access to one or more interfaces, and/or sub-interfaces, forpermissioning an authenticated user account to access the selectedgroup-based communication channel (as illustrated, #engineering). Insome such embodiments, user interaction with the member adding element654 provides one or more user selection interfaces for inputting anauthenticated user account associated with an organization and/orworkspace having access to the selected group-based communicationchannel. In this regard, the authenticated user account may be selectedfrom the authenticated user accounts associated with a higher-levelentity than the selected group-based communication channel.

As illustrated, the channel member management interface 650 furtherincludes an accessible workspace list 656. The accessible workspace listincludes an interface element associated with each workspace with whichthe selected group-based communication channel is shared. In thisregard, the selected group-based communication channel may be accessiblefrom within each workspace identified in the accessible workspace list656, as well as an owner workspace (such as the workspace within whichthe selected group-based communication channel was originally created).In some embodiments, the accessible workspace list 656 includesinformation associated with each workspace of the owner organizationwith which the selected group-based communication channel is shared, forexample at least a workspace name (e.g., “Bold Croutons”) and aworkspace identifier (e.g., “boldcroutons.slack.com”). Additionally oralternatively, in at least some embodiments, the accessible workspacelist 656 includes, or is otherwise associated with, one or moreinterface elements for managing the shared workspaces embodied in theaccessible workspace list. For example, in some embodiments, an “edit”interface element is rendered that, in response to user interaction,causes rendering of an interface and/or sub-interface including one ormore interface elements for generating and storing, via a group-basedcommunication system, data enabling access to the group-basedcommunication channel within an existing workspace (such as datarepresenting the workspace has been shared), and/or deleting dataenabling access from a workspace with which the selected group-basedcommunication channel was shared. In this regard, such an interfaceand/or sub-interface may include one or more interface elements forsearching, filtering, and/or sorting workspaces that are associated withthe owner organization for the selected group-based communicationchannel and with which the selected group-based communication channelmay be shared. In some such embodiments, the “edit” interface element isrendered in a circumstance where the authenticated user accountaccessing the channel member management interface 650 is permissionedfor managing workspace sharing for the selected group-basedcommunication channel.

As illustrated, the channel member management interface 650 furtherincludes a shared third-party organization list 658. The sharedthird-party organization list 658 includes an interface elementassociated with each third-party organization with which the selectedgroup-based communication channel is shared. In this regard, theselected group-based communication channel may be accessible by one ormore authenticated user accounts associated with each organizationrepresented in the shared third-party organization list 658. In someembodiments, the shared third-party organization list 658 includesinformation associated with each organization represented in the sharedthird-party organization list 658, for example at least an organizationname (e.g., “Bread Consulting”), and/or organization identifier, and anorganization member count (e.g., 4 authenticated user accountsassociated with the third-party organization). In some embodiments, an“edit” interface element is rendered that, in response to userinteraction, causes rendering of an interface and/or sub-interfaceincluding one or more interface elements for generating and/or storing,via a group-based communication system, data enabling access to thegroup-based communication channel by one or more authenticated useraccounts associated with a third-party organization, for example fromwithin one or more associated workspace(s), and/or for deleting dataenabling access to the group-based communication channel for one or moreauthenticated user accounts associated with a third-party organization(e.g., terminating the sharing of the selected group-based communicationchannel with the third-party organization). In some such embodiments,the “edit” interface element is rendered in a circumstance where theauthenticated user account accessing the channel member managementinterface 650 is permissioned for managing organization sharing for theselected group-based communication channel.

As illustrated, the channel member management interface 650 furtherincludes a posting permission interface element 660. The postingpermission interface element 660 includes information indicating usergroups, roles, and/or the like, permissioned for posting within theselected group-based communication channel. For example, in an examplecontext, all authenticated user accounts having access to the selectedgroup-based communication channel are permissioned to post group-basedcommunication messages to the selected group-based communicationchannel. In other contexts, only authenticated user accounts associatedwith one or more user roles (e.g., only administrator user accounts forthe authenticated user accounts, channel owner authenticated useraccounts, and/or the like), authenticated user accounts associated witha subset of the shared workspaces (for example, where authenticated useraccounts associated with only certain workspaces are permissioned forposting group-based communication messages to the selected channel),and/or authenticated user accounts associated with a subset of sharedorganizations (for example, where authenticated user account(s)associated with one or more third-party organizations are permissionedfor access and viewing but not for posting group-based communicationmessages to the selected channel). In some embodiments, an “edit”interface element is rendered that in response to user interaction,causes rendering of an interface and/or sub-interface including one ormore interface elements for editing permission data associated withposting to the selected group-based communication channel. For example,in some such embodiments, one or more interface elements may be providedfor inputting one or more authenticated user accounts to be permissionedfor posting to the selected group-based communication channel, one ormore user roles to be permissioned for posting to the selectedgroup-based communication channel, adding data representing one or moreworkspaces to permission for posting, deleting data for one or moreworkspaces not permissioned for posting, adding data representing one ormore organizations permissioned for posting, and/or deleting datarepresenting one or more organizations permissioned for posting, and/orthe like. In some such embodiments, the “edit” interface element isrendered in a circumstance where the authenticated user accountaccessing the channel member management interface 650 is permissionedfor managing posting permissions for the selected group-basedcommunication channel.

FIG. 7 illustrates an example channel access permissioning interface 700(“interface 700”) for managing access to one or more channel(s), inaccordance with at least one example embodiment of the presentdisclosure. In some embodiments, the interface 700 is rendered inresponse to user interaction with one or more interface elements forinitiating a channel management action for one or more selectedchannels. The channel access permissioning interface 700 is configuredto enable removing permission associated with one or more authenticateduser account(s) from accessing the associated channel(s), and/orgranting permission to one or more authenticated user accounts foraccessing the associated channel(s). In at least one embodiment, theinterface 700 is configured for rendering in a group-based communicationinterface and/or as a modal interface associated with a group-basedcommunication interface.

The interface 700 includes a channel access parameter element 702. Thechannel access parameter element 702 is configured for selecting aparameter value representing access to one or more associated channels.For example, in some such embodiments, each parameter value may define adifferent predefined methodology for providing permission data foraccessing the one or more group-based communication channels.Non-limiting examples of parameter values for providing permission datafor accessing the one or more group-based communication channel(s)include channel creator (or in other words an owner) only, channelcreator and administrator user accounts, and/or channel creator,administrator user accounts, and/or one or more designated useraccounts.

In some such embodiments, additionally or alternatively, the interface700 includes the designated user selection element 704. In someembodiments, a user may interact with the designated user selectionelement 704 to provide input for adding one or more authenticated useraccount(s) to be permissioned for accessing the associated group-basedcommunication channel(s) and/or remove permission for accessing theassociated group-based communication channel(s). In this regard, thedesignated user selection element 704 may include authenticated useraccount identifier(s), and/or associated information such as a nameassociated with the authenticated user account, to be permissioned foraccessing the group-based communication channel(s). Accordingly, thedesignated user selection element 704 may include a sub-interface foreach authenticated user account permissioned to access the group-basedcommunication channel(s). In some such embodiments, interaction with thedesignated user selection element 704 and/or the sub-interface thereofassociated with a particular authenticated user account, enables removalof permission data for the authenticated user account with respect tothe group-based communication channel(s) upon submission.

As illustrated, the interface 700 further includes an interface cancelelement 706. The interface cancel element 706 may be configured toreceive user interaction representing cancellation of managing thegroup-based communication channel(s) via the interface 700. In thisregard, interaction with the interface cancel element 706 may causerendering of a centralized channel management dashboard 500 withoutstoring data for permanently effecting changes made via the interface700. Further as illustrated, the interface 700 further includes aninterface submission element 708. The interface submission element 708may be configured to receive user interaction representing saving of thevalues input via the interface 700. In this regard, interaction with theinterface submission element 708 may initiate one or more processes tocause storage of the input values in a group-based communication system,for example to store permission data only associated with authenticateduser accounts indicated as having permission for accessing and/ormanaging the one or more identified group-based communication channels.In some such embodiments, interaction with the interface submissionelement 708 causes transmission of data representing input via theinterface 700 to a group-based communication system for processingand/or storing. In some embodiments, upon determining the input valueshave been successfully stored via a group-based communication system(for example, based on a response transmission from the group-basedcommunication system), a centralized channel management dashboard 500 isagain rendered via the client device to enable initiation of subsequentchannel management actions for one or more manageable group-basedcommunication channels.

In at least some embodiments, a group-based communication interface maybe configured to include a sub-interface to convey, via one or moreinterface elements, channel information for one or more group-basedcommunication channels. In at least some embodiments, such channelinformation includes permission data regarding access to and/ormanagement of the one or more group-based communication channels. Inthis regard, FIG. 8 illustrates an example channel information interface800 (“interface 800”) that notifies a user of which organizations (orother user groups, for example associated with another workspace) haveaccess to a group-based communication channel, in accordance with atleast one example embodiment of the present disclosure. In the at leastone embodiment, the interface 800 is configured to include one or moresub-interfaces for conveying such channel information for one or moregroup-based communication channels.

As illustrated, the channel information interface 800 includes a channelprivacy notification element 802. In some embodiments, the channelprivacy notification element 802 is configured to include datarepresenting one or more entities, and/or authenticated user accountsassociated therewith, permissioned to access a group-based communicationchannel. In this regard, a group-based communication system may identifysuch entities based on channel information associated with thegroup-based communication channel(s). For example, in at least oneembodiment, the group-based communication system may be configured toidentify one or more third-party organization identifiers and/orworkspace identifiers with which the group-based communication channelis shared, and provide such information to a client device for renderingvia an interface element, such as the channel privacy notificationelement 802.

In this regard, the channel privacy notification element 802 may beprocessed, and/or analyzed, to identify desired changes in access to theone or more group-based communication channels. In some embodiments, theinterface 800 includes one or more additional interface elements foraccessing functionality for managing at least the group-basedcommunication. For example, as illustrated, the interface 800 includeschannel management interface transition element 804. In someembodiments, the channel management interface transition element 804 isconfigured to initiate rendering of a centralized channel managementdashboard for viewing and/or managing channel information for at leastthe group-based communication channel(s) associated with the interface800. Accordingly, in some such embodiments, a user may interact with thechannel management interface transition element 804 to transmit one ormore requests to a group-based communication system configured such thatthe group-based communication system causes rendering of a centralizedchannel management dashboard, for example centralized channel managementdashboard 500. In this regard, in at least some contexts, the interface800 is configured to enable streamlined and efficient access tofunctionality for managing one or more selected group-basedcommunication channel(s).

The channel information interface 800 may additionally or alternativelyinclude elements associated with various other functionality formanaging group-based communication channel access. For example, in atleast one embodiment, the channel information interface 800 includes oneor more interface elements for configuring a group-based communicationchannel as a private group-based communication channel and/or publicgroup-based communication channel. In this regard, such interfaceelements may be interacted with to configure a corresponding setting toalter access permissions for one or more users accordingly, for examplesuch that all authenticated user accounts of a particular workspace arepermissioned for accessing the group-based communication channel if thegroup-based communication channel is set to a public group-basedcommunication channel, and such that a limited set of authenticated useraccounts of a particular workspace are permissioned for accessing thegroup-based communication channel if the group-based communicationchannel is set to a private group-based communication channel.Additionally or alternatively, for example in at least one embodiment,the channel information interface 800 includes one or more interfaceelements for sharing a group-based communication channel, for examplethe group-based communication channel, with one or more other workspacesassociated with the organization owning the group-based communicationchannel. In at least one example context, the channel informationinterface 800 may provide a dropdown element for selecting from otherworkspaces with which to share the selected group-based communicationchannel. Additionally or alternatively, in at least one embodiment, thechannel information interface 800 includes one or more interfaceelements for sharing the group-based communication channel with one ormore third-party organizations (such as an organization other than theowner organization).

In some embodiments, the above-described functionality is provided viaone or more APIs made available via the group-based communicationsystem, for example embodied by the apparatus 200, which in someembodiments may further be accessed without use of one or moreinterface(s) through various requests. In this regard, the client devicemay request and/or receive data from a group-based communication system,and subsequently process the received data and/or perform furtherrequests based on the received data without user interaction with anysuch interfaces, and/or without any user interaction at all. Forexample, in some embodiments, one or more requests may be performedautomatically via communication with the group-based communicationsystem utilizing one or more APIs, and/or the response data receivedfrom the group-based communication system may be automatically processedand one or more corresponding actions performed based on at least on thereceived data. Additionally or alternatively, in at least someembodiments, the data received via the one or more API requests isutilized in rendering one or more of the interfaces described above.

Example Operations for Centralized Channel Management

FIGS. 9-14 illustrate flowcharts depicting various example operationsfor processes and/or sub-processes for centralized channel management,in accordance with at least some example embodiments of the presentdisclosure. In at least some embodiments the described processes areperformed via a group-based communication system, for example embodiedby the apparatus 200 as depicted and described with respect to FIG. 2 .In some embodiments, the apparatus 200 is in communication with one ormore additional systems, devices, apparatuses, and/or the like, toenable one or more of the operations described herein. For example, insome embodiments, the apparatus is in communication with one or moreexternal resource(s) and/or at least one client device, where the clientdevice may be embodied by the specially configured apparatus 300 asdepicted and described above with respect to FIG. 3 . It should beappreciated that the apparatus 200 may be configured to communicate withthe external resource(s) and/or client device(s) over one or morecommunication networks, such as the Internet.

As illustrated in the various flowcharts, optional blocks are depictedwith dashed (or “broken”) lines. It should be appreciated that, in atleast some embodiments, one or more of the optional blocks is performed.Additionally or alternatively, in at least one embodiment, none of theoptional blocks is performed. Additionally or alternatively still, inyet at least one other embodiment, all of the optional blocks areperformed. It should also be appreciated that, in some embodiments, oneor more blocks (whether indicated as optional or not) may be droppedfrom the embodiment processes as depicted and described. For example,with reference to FIG. 9 depicted and described herein, an exampleprocess may include at least blocks 902, 904, and 906, and may notinclude the blocks 908, 910, and/or 912. Alternatively in otherembodiments, another example process may include at least blocks 908,910, and/or 912, and may not include blocks 902, 904, and/or 906. Inthis regard, one or more sub-combinations of blocks may represent aprocess and/or subprocess performed by one or more embodiments intendedto be covered by the disclosure provided herein.

FIG. 9 illustrates example operations for an example process forcentralized channel management, in accordance with at least some exampleembodiments of the present disclosure. At optional block 902, theapparatus 200 includes means, such as the central channel managementmodule 212, the group-based communication module 210, the communicationsmodule 208, the input/output module 206, the processor 202, and/or thelike, or a combination thereof, configured to receive, from a clientdevice, a centralized channel management request. In some embodiments,the centralized channel management request is associated with anauthenticated user account identifier. The authenticated user accountidentifier uniquely identifies an authenticated user account accessingthe apparatus 200, for example during an authenticated session. In thisregard, the authenticated user account identifier may represent a uniqueidentifier for use in identifying group-based communication channelspermissioned for management by the authenticated user account accessingthe apparatus 200. In some embodiments, the authenticated user accountidentifier is included in the centralized channel management request,such that the apparatus 200 may parse the authenticated user accountidentifier from the request. Additionally or alternatively, in at leastsome embodiments, the apparatus 200 is configured to identify theassociated authenticated user account based on an authenticated sessionfor the client device from which the request was received. For example,the apparatus 200 may be configured to validate the client device isassociated with an existing authenticated session, and thus identify aparticular authenticated user account associated with the authenticatedsession upon and/or during validation.

At optional block 904, the apparatus 200 includes means, such as thecentral channel management module 212, the group-based communicationmodule 210, the communications module 208, the input/output module 206,the processor 202, and/or the like, or a combination thereof, configuredto identify a group-based communication channel metadata set for one ormore group-based communication channels. In at least some embodiments,for example, the apparatus 200 is configured to identify a group-basedcommunication channel metadata set for each group-based communicationchannel in a manageable group-based communication channel setpermissioned for management by an authenticated user account associatedwith the authenticated user account identifier. In some suchembodiments, the manageable group-based communication channel set may beidentified using the authenticated user account identifier receivedand/or identified at an earlier block, for example at block 902.

The apparatus 200 may identify permission data associated with theauthenticated user account identifier and utilize such permission datato identify the manageable group-based communication channel set. Forexample, in a circumstance where the apparatus 200 queries forpermission data associated with the authenticated user accountidentifier and retrieves permission data indicating the authenticateduser account is an administrator user account for an organization, theapparatus 200 may identify all group-based communication channels as asub-entity of the organization and include the group-based communicationchannels in the manageable group-based communication channel set.Additionally or alternatively, in a circumstance where the apparatus 200retrieves permission data indicating the authenticated user account isan administrator user account for a workspace, the apparatus 200 mayidentify all group-based communication channels as a sub-entity of theworkspace and include the group-based communication channels in themanageable group-based communication channel set. Additionally oralternatively, in a circumstance where the apparatus 200 retrievespermission data indicating the authenticated user account is anadministrator user account, and/or otherwise is associated with datadesignating the authenticated user account identifier as anadministrator user account, for the group-based communication channel,the apparatus 200 may include the group-based communication channel inthe manageable group-based communication channel set. In this regard,the manageable group-based communication channel set may represent apersonalized set of group-based communication channels manageable by theauthenticated user account identifier based on assigned permission data.

At optional block 906, the apparatus 200 includes means, such as thecentral channel management module 212, the group-based communicationmodule 210, the communications module 208, the input/output module 206,the processor 202, and/or the like, or a combination thereof, configuredto transmit, to the client device, the group-based communicationmetadata set. In some embodiments, the group-based communicationmetadata set includes, or otherwise embodies, a set of channelinformation for each of the manageable group-based communicationchannels. In this regard, the group-based communication metadata set maybe processed and/or analyzed to identify one or more group-basedcommunication channels for managing via one or more channel managementactions. In some embodiments, the apparatus 200 is configured to causerendering of a centralized channel management dashboard by transmittingthe group-based communication channel metadata set to the client device.The centralized channel management dashboard may be specially configuredfor displaying the group-based communication channel metadata set in adesired and/or efficient layout that enables improved processing and/oranalysis of the metadata set, for example to identify one or moregroup-based communication channels requiring management. Additionally oralternatively, in some embodiments, for example as described herein, thecentralized channel management dashboard includes one or more interfaceelements for filtering and/or otherwise limiting data rendered withinthe dashboard, and/or for initiating one or more channel managementactions.

At optional block 908, the apparatus 200 includes means, such as thecentral channel management module 212, the group-based communicationmodule 210, the communications module 208, the input/output module 206,the processor 202, and/or the like, or a combination thereof, configuredto receive, from the client device, channel management data associatedwith a selected group-based communication channel of the manageablegroup-based communication channel set. The channel management data mayembody one or more requests to alter one or more parameter valuesassociated with the selected group-based communication channel. Forexample, in at least one example context, the channel management dataembodies a set of authenticated user account identifiers to bepermissioned for managing accessing the selected group-basedcommunication channel, such that the identified authenticated useraccounts may grant or revoke permission data to other authenticated useraccounts for accessing the selected group-based communication channel.Alternatively or additionally, in another example context, the channelmanagement data embodies a set of organization identifiers (and/orworkspace identifiers) for which the selected group-based communicationchannel is to be shared.

In at least some embodiments, the channel management data is received inresponse to user interaction with the centralized channel managementdashboard. For example, in some embodiments, the channel management datais received in response to user interaction with one or more channelmanagement interface element(s) rendered via the dashboard. In thisregard, it should be appreciated that the channel management interfaceelement may be specially configured to transmit channel management dataassociated with a particular selected group-based communication channelof the manageable group-based communication channel set in response touser interaction.

It should be appreciated that the channel management data may representa request for altering parameter values for a plurality of selectedgroup-based communication channels. For example, a user may request thatall manageable group-based communication channels of a certain channeltype (e.g., all public common group-based communication channels) haveaccess managed by a particular set of authenticated user accountsidentified by the channel management data. In this regard, the channelmanagement data may be associated with a plurality of selectedgroup-based communication channels of the manageable group-basedcommunication channel set. In some such embodiments, the channelmanagement data includes a set of channel identifiers for the set ofselected group-based communication channels to be managed.

At optional block 910, the apparatus 200 includes means, such as thecentral channel management module 212, the group-based communicationmodule 210, the communications module 208, the input/output module 206,the processor 202, and/or the like, or a combination thereof, configuredto process the channel management data to update the selectedgroup-based communication channel. In this regard, the apparatus 200 maybe configured to store an updated value represented by the channelmanagement data for one or more parameter values, and/or other storedinformation, associated with the selected group-based communicationchannel. For example, in an example context where the set ofauthenticated user accounts permissioned for managing access to theselected group-based communication channel is updated, the apparatus 200may delete permission data associated with authenticated user accountidentifiers no longer identified in the channel management data, andstore permission data associated with authenticated user accountidentifiers newly identified in the channel management data. In otherembodiments, for example in a circumstance where the channel managementdata is associated with a plurality of selected group-basedcommunication channels, the apparatus 200 may be configured to processthe channel management data to update the plurality of selectedgroup-based communication channels.

In some embodiments, upon updating the selected group-basedcommunication channel(s), the apparatus 200 may generate and/or transmitone or more response transmissions to the client device indicatingsuccessful processing of the channel management data. Alternatively oradditionally, in at least some embodiments, the response transmission(s)are configured to cause updating of data rendered via a centralizedchannel management dashboard. In this regard, in such contexts, theapparatus 200 may be configured to enable real-time management andprocessing of channel information associated with any number ofgroup-based communication channels.

In some embodiments, the apparatus 200 generates a new group-basedcommunication message posted within the selected group-basedcommunicating channel(s) upon successfully managing the selectedgroup-based communication channel(s). In some such embodiments, thegenerated new group-based communication message provides predefinedsummary information regarding one or more management actions performedfor the channel. For example, in a circumstance where a channel renameaction is successfully processed, the apparatus 200 may generate agroup-based communication message for the selected group-basedcommunication channel that indicates an administrator has renamed theselected group-based communication channel(s) (e.g., includes themessage contents “An administrator has renamed this channel.”). In thisregard, the new group-based communication messages may providenotification information to users accessing the selected group-basedcommunication channel(s). For example, the new group-based communicationmessage may be rendered to a group-based communication interface in acircumstance where a use accesses any of the selected group-basedcommunication channel(s), via an authenticated user account, from withinthe group-based communication interface.

At optional decision block 912, the apparatus 200 includes means, suchas the central channel management module 212, the group-basedcommunication module 210, the communications module 208, theinput/output module 206, the processor 202, and/or the like, or acombination thereof, configured to determine whether new channelmanagement data was received. In this regard, the apparatus 200 may beconfigured to receive any number of channel management data during oneor more authenticated sessions. For example, a user may submit one ormore requests via an API maintained by the apparatus 200, and thus theapparatus 200 may receive new channel management data in response to oneor more new API requests. Alternatively or additionally, in someembodiments, new channel management data is received in response tosubsequent user interaction with a rendered centralized channelmanagement dashboard. For example, a user may initiate various requestsfor configuring group-based communication channels of different channeltypes. In some such embodiments in a circumstance where the apparatusdetermines new channel management data is received, flow returns to 908and the new channel management data may be processed by the apparatus200. In a circumstance where the apparatus 200 determines new channelmanagement data was not received, the flow may end.

FIG. 10 illustrates example additional operations for an example processfor centralized channel management, specifically to identify agroup-based communication metadata set for one or more group-basedcommunication channel, in accordance with at least some exampleembodiments of the present disclosure. In some embodiments, one or moreof the blocks of FIG. 10 is additional to, and/or replaces, one or moreblocks of another process. For example, as illustrated, in someembodiments, the process begins after one or more blocks of FIG. 9 , forexample after optional block 902. Additionally or alternatively, in someembodiments, flow returns to one or more other processes describedherein after completion of the process as depicted and described withrespect to FIG. 10 . For example, as illustrated, in some embodiments,the process returns to block 906 as depicted and described with respectto FIG. 9 after completion of block 1004 as depicted and described withrespect to FIG. 10 .

At block 1002, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toidentify a group-based communication identifier set associated with themanageable group-based communication channel set. In this regard, theapparatus 200 may be configured to identify the manageable group-basedcommunication channel set based on at least the authenticated useraccount identifier. In this regard, the apparatus 200 may query for thegroup-based communication channel identifier for each identifiedmanageable group-based communication channel. It should be appreciatedthat, in some embodiments, the manageable group-based communicationchannel set embodies the group-based communication channel identifierset for the manageable group-based communication channels associatedwith the authenticated user account identifier.

At block 1004, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toquery a channel datastore based on the group-based communication channelset to receive each group-based communication channel metadata set foreach group-based communication channel identifier in the group-basedcommunication channel identifier set. In some such embodiments, theapparatus 200 receives a set of group-based communication metadata sets,representing each group-based communication channel metadata setassociated with each group-based communication channel identifier in thegroup-based communication channel identifier set, from the channeldatastore in response to the query. It should be appreciated that thegroup-based communication channel metadata set may include variouschannel information. For example, each group-based communicationmetadata set may include one or more parameter values of the group-basedcommunication channel (e.g., a channel name, channel type, sharedstatus, or the like) or information derived and/or otherwise associatedwith the group-based communication channel (e.g., authenticated useraccounts permissioned to access the channel as a member, third-partyorganization identifiers and/or other information with which the channelis shared). In various embodiments, the apparatus 200 may be configuredto receive any type of channel information, and/or information derivedtherefrom and/or otherwise associated with such channel information, forprocessing and/or analysis by a user, or otherwise useful in one or moredecision-making processes for determining whether to manage thegroup-based communication channel.

FIG. 11 further illustrates example additional operations for an exampleprocess for centralized channel management, specifically to identify agroup-based communication metadata set for one or more group-basedcommunication channel, in accordance with at least some exampleembodiments of the present disclosure. In some embodiments, one or moreof the blocks of FIG. 11 is additional to, and/or replaces, one or moreblocks of another process. For example, as illustrated, in someembodiments, the process begins after one or more blocks of FIG. 9 , forexample after optional block 902. Additionally or alternatively, in someembodiments, flow returns to one or more other processes describedherein after completion of the process as depicted and described withrespect to FIG. 11 . For example, as illustrated, in some embodiments,the process returns to block 906 as depicted and described with respectto FIG. 9 after completion of block 1104 as depicted and described withrespect to FIG. 11 .

At block 1102, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured todetermine the authenticated user account identifier is associated withworkspace permission data linked to a workspace identifier. In thisregard, the workspace permission data may embody specific permissiondata indicating the authenticated user account embodies an administratoruser account with respect to the workspace and/or otherwise isdesignated for managing the workspace identified by the workspaceidentifier and/or sub-entities thereof. In some embodiments, todetermine the authenticated user account identifier is associated withworkspace permission data linked to the workspace identifier, theapparatus 200 is configured to query one or more datastores. Forexample, in at least some embodiments, the apparatus 200 may query oneor more datastores based on the authenticated user account identifierand receive at least the workspace permission data linked to theworkspace identifier in response to the query.

At block 1104, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toidentify each group-based communication channel metadata set for atleast one group-based communication channel associated with theworkspace identifier. In this regard, for example, the apparatus 200 maybe configured to identify a group-based communication channel setembodying sub-entities of the workspace identified by the workspaceidentifier. Such group-based communication channels may be “within” theworkspace, such that the workspace permission data indicates theauthenticated user account is permissioned for managing suchsub-entities associated with the workspace identifier as well. In somesuch embodiments, the apparatus 200 may be configured to identify the atleast one group-based communication channel associated with theworkspace identifier by querying at least one datastores for group-basedcommunication channels associated with the workspace identifier, andreceiving the at least one group-based communication channel in responseto the query. In some such circumstances, the group-based communicationchannel metadata set for each group-based communication channel maysubsequently be parsed from the retrieved at least one group-basedcommunication channel, and/or retrieved based on information retrievedfor the at least one group-based communication channel. For example, insome embodiments where the query for the at least one group-basedcommunication channel associated with the workspace identifier retrievesonly channel identifiers for such group-based communication channels,the apparatus 200 may be configured to perform one or more additionalqueries to retrieve the group-based communication metadata set for eachgroup-based communication identifier.

FIG. 12 further illustrates example additional operations for an exampleprocess for centralized channel management, specifically to identify agroup-based communication metadata set for one or more group-basedcommunication channel, in accordance with at least some exampleembodiments of the present disclosure. In some embodiments, one or moreof the blocks of FIG. 12 is additional to, and/or replaces, one or moreblocks of another process. For example, as illustrated, in someembodiments, the process begins after one or more blocks of FIG. 9 , forexample after optional block 902. Additionally or alternatively, in someembodiments, flow returns to one or more other processes describedherein after completion of the process as depicted and described withrespect to FIG. 12 . For example, as illustrated, in some embodiments,the process returns to block 906 as depicted and described with respectto FIG. 9 after completion of block 1204 as depicted and described withrespect to FIG. 12 .

In this regard, the apparatus 200 may be configured to determination aparticular authenticated user account is permissioned for managing anorganization. Additionally or alternatively, based at least on thisdetermination, the apparatus 200 may be configured to identify allworkspaces associated with, owned by, and/or otherwise accessible to theorganization. Such entities may be identified to provide suchinformation to a client device associated with the authenticated useraccount, and/or to provide functionality for managing such entities. Forexample, in some such embodiments, the apparatus 200 is configured toidentify a set of workspaces, and a set of channel identifiers for eachmanageable channel within the workspace. Additionally or alternativelystill, the apparatus 200 may retrieve channel information for eachchannel, for example to provide such information to a client deviceassociated with the authenticated user account, and/or to providefunctionality for managing such group-based communication channels. Inthis regard, the apparatus 200 may provide one or more APIs foridentifying such information associated with one or more entities,and/or for performing one or more associated actions for managing suchentities. It should be appreciated that the API may be accessiblethrough one or more interfaces as described herein, and/or in at leastsome embodiments may be accessed directly through one or morecorresponding request(s) as described herein.

At block 1202, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured todetermine the authenticated user account identifier is associated withorganization permission data linked to an organization identifier. Theorganization permission data may be associated with one or more entitytypes, for example group-based communication channel types, such thatthe authenticated user account is permissioned for managing allgroup-based communication channels associated with the permissionedchannel type in any workspace associated with the organization. In thisregard, the organization permission data may embody specific permissiondata indicating an authenticated user account embodies an administratoruser account with respect to the organization identified by theorganization identifier, and/or otherwise is designated for managing theorganization identified by the organization identifier and/orsub-entities thereof. In some embodiments, to determine theauthenticated user account identifier is associated with organizationpermission data linked to the organization identifier, the apparatus 200is configured to query one or more datastores. For example, in at leastsome embodiments, the apparatus 200 may query one or more datastoresbased on the authenticated user account identifier and receive at leastthe organization permission data linked to the organization identifierin response to the query (or queries). In some such embodiments, theapparatus 200 is configured to query one or more user datastoresincluding such permission data associated with the authenticated useraccount identifier and organization identifier, and/or one or morepermission data datastores including such permission data associatedwith the authenticated user account identifier and organizationidentifier.

At block 1202, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toidentify each group-based communication metadata set for at least onegroup-based communication channel associated with the organizationidentifier. In this regard, the apparatus 200 may be configured toidentify a group-based communication channel set embodying sub-entitiesof the organization identified by the organization identifier. Suchgroup-based communication channels may be “within” the organization,and/or within one or more workspaces associated with the organization,such that the organization permission data indicates the authenticateduser account is permissioned for managing such group-based communicationchannels as sub-entities of the organization. In some such embodiments,the apparatus 200 may be configured to identify group-basedcommunication channel(s) associated with the organization identifier byquerying at least one datastores based on the organization identifier,and receiving the group-based communication channel set in response tothe query. Alternatively or additionally, the apparatus 200 may identifya set of workspace identifiers associated with the organizationidentifier (e.g., for workspaces that are sub-entities of theorganization identifier), and further query for the group-basedcommunication channel set based on the set of workspace identifiers. Insome such circumstances, the group-based communication channel metadataset for each group-based communication channel may subsequently beparsed from the retrieved group-based communication channel(s), and/orretrieved based on the information retrieved for each group-basedcommunication channel. For example, in some embodiments where the queryfor the at least one group-based communication channel associated withthe organization retrieves only channel identifiers for such group-basedcommunication channels, the apparatus 200 may be configured to performone or more additional queries to retrieve the group-based metadata setfor each group-based communication identifier.

FIG. 13 further illustrates example additional operations for an exampleprocess for centralized channel management, specifically to identify agroup-based communication metadata set for one or more group-basedcommunication channel, in accordance with at least some exampleembodiments of the present disclosure. In some embodiments, one or moreof the blocks of FIG. 13 is additional to, and/or replaces, one or moreblocks of another process. For example, as illustrated, in someembodiments, the process begins after one or more blocks of FIG. 9 , forexample after optional block 902. Additionally or alternatively, in someembodiments, flow returns to one or more other processes describedherein after completion of the process as depicted and described withrespect to FIG. 13 . For example, as illustrated, in some embodiments,the process returns to block 906 as depicted and described with respectto FIG. 9 after completion of block 1304 as depicted and described withrespect to FIG. 13 .

At block 1302, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured todetermine the authenticated user account identifier is associated withchannel owner data or delegated management data for a privategroup-based communication channel. In some embodiments, for example, theapparatus 200 is configured to store channel owner data for eachgroup-based communication channel, and is configured to identify thegroup-based communication channels where such channel owner datarepresents the authenticated user account identifier. Alternatively oradditionally, in at least some embodiments, the apparatus 200 isconfigured to store, for each group-based communication channel,delegated management data associated with the group-based communicationchannel that indicates the user has been granted permissions formanaging one or more settings of the group-based communication channelassociated with the delegated management data. In some such embodiments,the apparatus 200 is configured to query one or more datastores forchannel owner data and/or delegated management data representing theauthenticated user account identifier, and determine the group-basedcommunication channel(s) associated with such data based on informationreceived in response to the query or queries.

It should be appreciated that, in some embodiments, an authenticateduser account associated with channel owner data and/or delegatedmanagement data for a particular group-based communication channel maybe determined for any of a number of channel types. For example asillustrated, the apparatus 200 may determine the channel owner dataand/or delegated management data is associated with a privategroup-based communication channel. In some such embodiments, the privategroup-based communication channel may be configured such that onlyauthenticated user account identifiers represented by the channel ownerdata and/or delegated management data for the private group-basedcommunication channel, and/or a higher-level entity, are permissioned tomanage the private group-based communication channel. In this regard, insome embodiments, the authenticated user account identifier need not bepermissioned to access the private group-based communication channel oreven an associated workspace. Instead, the authenticated user accountmay be associated with permission data for managing the privategroup-based communication channel and/or a higher level entityregardless of whether the authenticated user account is alsopermissioned for accessing the private group-based communicationchannel. In circumstances where private group-based communicationchannels require additional configuration to access the privategroup-based communication channel, (e.g., an invitation to the privategroup-based communication channel is sent from an administrator of theprivate group-based communication channel to the authenticated useraccount, then accepted by the authenticated user account), processingresources associated with such an invitation process are conserved byenabling direct management of the private group-based communicationchannel without such access to the channel.

At block 1304, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toidentify at least a group-based communication metadata set for theprivate group-based communication channel. In some embodiments, thegroup-based communication metadata set is retrieved from one or moredatastores configured for storing data embodying and/or associated witheach group-based communication channel. In some embodiments, forexample, a channel identifier for the private group-based communicationchannel may be identified at one or more earlier steps, for example atblock 1302. In some such embodiments, the apparatus 200 may beconfigured to identify the group-based communication metadata set forthe private group-based communication channel by querying one or moredatastores based on the determined group-based communication channelidentifier.

FIG. 14 further illustrates example additional operations for an exampleprocess for centralized channel management, specifically to providechannel privacy access data associated with a selected group-basedcommunication channel, in accordance with at least some exampleembodiments of the present disclosure. In some embodiments, one or moreof the blocks of FIG. 14 is additional to, and/or replaces, one or moreblocks of another process. For example, as illustrated, in someembodiments, the process begins after one or more blocks of FIG. 9 , forexample after optional block 902. Additionally or alternatively, in someembodiments, flow returns to one or more other processes describedherein after completion of the process as depicted and described withrespect to FIG. 14 . For example, as illustrated, in some embodiments,the process returns to block 906 as depicted and described with respectto FIG. 9 after completion of block 1304 as depicted and described withrespect to FIG. 14 .

At block 1402, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toreceive, from a second client device associated with a secondauthenticated user account, a selected channel information request for aselected communication channel. In some embodiments, the selectedchannel information request represents a request to for informationregarding entities having access to data posted to and/or otherwisetransmitted within a selected group-based communication channel. Forexample, the selected group-based communication channel may represent agroup-based communication channel that the second authenticated useraccount is accessing, or otherwise permissioned to access. In someembodiments, the selected channel information request includes at leasta channel identifier for the selected group-based communication channel.

In some embodiments, the apparatus 200 is configured to receive theselected channel information request from the second client device inresponse to one or more user interactions via the second client device.For example, in some embodiments, the selected channel informationrequest is received via one or more APIs made available via theapparatus 200. Additionally or alternatively, in some embodiments, theselected channel information request is received from the client devicein response to user interaction with one or more elements of aninterface rendered via the second client device. For example, in someembodiments, the selected channel information request is received inresponse to user interaction with a group-based communication channel,for example to select the select group-based communication channel, torequest information associated with the selected group-basedcommunication channel after selection, automatically when rendering oneor more sub-interfaces associated with the selected group-basedcommunication channel (e.g., a sharing interface or other channelmanagement interface, such as the interface 800 as depicted anddescribed above with respect to FIG. 8 ), and/or in response to one ormore user interactions with interface elements specifically configuredfor requesting information for one or more selected group-basedcommunication channels. In some embodiments, the selected channelinformation request is transmitted from within a centralized channelmanagement dashboard.

At block 1404, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured toidentify, based on group-based communication metadata set associatedwith the selected group-based communication channel, channel privacyaccess data associated with the selected group-based communicationchannel. In this regard, the channel privacy access data may indicateone or more sets of authenticated user accounts having access to thegroup-based communication channel. Such sets of authenticated useraccounts may, in some embodiments, be defined by authenticated useraccounts associated with one or more organizations and/or workspaceswith which the channel is shared. For example, if the group-basedcommunication channel is publicly shared with the organization “ACME,”the channel privacy access data may identify the ACME organizationand/or otherwise include data indicating ACME has access to thegroup-based communication channel. In this regard, the channel privacyaccess data may embody data derived from some or all of the group-basedcommunication channel metadata set for the selected group-basedcommunication channel. For example, the identified group-basedcommunication channel metadata set may include the organizationidentifiers and/or workspace identifiers with which the selectedgroup-based communication channel is shared, and/or one or moreauthenticated user account identifiers with which the selectedgroup-based communication channel is shared. In this regard, the channelprivacy access data derived therefrom may embody the identifiers for theorganization(s), workspace(s), and/or authenticated user account(s),and/or may represent other data, for example name data for eachorganization, workspace, and/or authenticated user, permissioned toaccess the selected group-based communication channel.

At block 1406, the apparatus 200 includes means, such as the centralchannel management module 212, the group-based communication module 210,the communications module 208, the input/output module 206, theprocessor 202, and/or the like, or a combination thereof, configured totransmit, to the second client device, the channel privacy access datafor processing. In some embodiments, the apparatus 200 is configured totransmit the channel privacy access data to cause the client device toinitiate one or more actions based on the channel privacy access data.For example, in one example context, the client device may furtherprocess the channel privacy access data to determine whether permissiondata should be revoked for one or more organization(s), workspace(s),and/or authenticated user account(s), and to cause the second clientdevice to initiate one or more transmissions for revoking suchpermission data. Alternatively or additionally in one example context,the client device may further process the channel privacy access data todetermine whether permission data should be granted for one or moreorganization(s), workspace(s), and/or authenticated user account(s) foraccessing the selected group-based communication channel (e.g. where thepermission data represents access to the selected group-basedcommunication channel and/or sharing of the group-based communicationchannel with one or more organization(s) and/or workspace(s)), and/or tocause the second client device initiate one or more transmissions forgranting such permission data. It should be appreciated that, in someembodiments, the apparatus 200 causes initiation of such transmissionsthrough the second client device in circumstances where the clientdevice is associated with an authenticated user account permissioned formanaging access to the selected group-based communication channel.

Alternatively or additionally, in some embodiments, the channel privacyaccess data is configured to be rendered to one or more interfacesrendered via the second client device. For example, in some embodiments,the apparatus 200 transmits the channel privacy access data to causerendering of channel privacy notification information based at least onthe channel privacy access data. In some embodiments, for example, theapparatus 200 may be configured to cause rendering of name informationderived based on the identified channel privacy access data, for examplewhere the name information indicates entities and/or users permissionedfor accessing the selected group-based communication channel. It shouldbe appreciated that, in some embodiments, the channel privacynotification information is embodied by the channel privacy access data.In some embodiments, the channel privacy notification informationenables a user to determine whether to revoke existing access for one ormore organizations, workspaces, and/or authenticated user accounts (forexample by generating and/or storing permission data), and/or grantingnew access to one or more organizations, workspaces, and/orauthenticated user accounts (for example by deleting stored permissiondata).

Example Client Device Operations for Centralized Channel Management

FIG. 15 illustrates a flowchart depicting various example operations forprocesses and/or sub-processes for centralized channel management, inaccordance with at least some example embodiments of the presentdisclosure. In at least some embodiments the described processes areperformed via a specially configured client device, for example embodiedby the apparatus 300 as depicted and described with respect to FIG. 3 .In some embodiments, the apparatus 300 is in communication with one ormore additional systems, devices, apparatuses, and/or the like, toenable one or more of the operations described herein. For example, insome embodiments, the apparatus 300 is in communication with at least agroup-based communication system, where the group-based communicationsystem may be embodied by the specially configured apparatus 200 asdepicted and described above with respect to FIG. 2 . It should beappreciated that the apparatus 300 may be configured to communicate withthe group-based communication system over one or more communicationnetworks, such as the Internet. In some embodiments, one or more of theoperation(s) are performed associated with one or more interfaces, forexample a centralized channel management dashboard. Additionally oralternatively, in some embodiments, one or more operation(s) areperformed via one or more APIs made available via the apparatus 300and/or a corresponding group-based communication system, for exampleembodied by the apparatus 200.

As illustrated in the various flowcharts, optional blocks are depictedwith dashed (or “broken”) lines. It should be appreciated that, in atleast some embodiments, one or more of the optional blocks is performed.Additionally or alternatively, in at least one embodiment, none of theoptional blocks is performed. Additionally or alternatively still, inyet at least one other embodiment, all of the optional blocks areperformed. It should also be appreciated that, in some embodiments, oneor more blocks (whether indicated as optional or not) may be droppedfrom the embodiment processes as depicted and described. In this regard,one or more sub-combinations of blocks may represent a process and/orsubprocess performed by one or more embodiments intended to be coveredby the disclosure provided herein.

FIG. 15 depicts example operations for an example process forcentralized channel management, in accordance with at least some exampleembodiments of the present disclosure. At optional block 1502, theapparatus 300 includes means, such as the group-based client module 310,communications module 308, input/output module 306, processor 302 and/orthe like, or a combination thereof, configured to transmit a centralizedchannel management request to a group-based communication system. Insome embodiments, the centralized channel management request isassociated with an authenticated user account identifier correspondingto an authenticated user account associated with an authenticatedsession. In at least some embodiments, the centralized channelmanagement request is transmitted automatically upon initiating anauthenticated session, and/or is otherwise embodied by the request toinitiate the authenticated session, and receive centralized channel datafrom the group-based communication system. Additionally oralternatively, in at least some embodiments, the apparatus 300 maygenerate and/or transmit the centralized channel management request tothe group-based communication system in response to a user-initiatedaction (e.g., launching a particular webpage, native app functionality,or the like). In some embodiments, for example, the user may interactwith an interface element of a group-based communication interface foraccessing a centralized channel management dashboard, causing theapparatus 300 to generate and/or transmit the centralized channelmanagement request automatically. Alternatively or additionally, in atleast some embodiments, the apparatus 300 is configured to transmit thecentralized channel management request via one or more APIs associatedwith the group-based communication system.

At block 1504, the apparatus 300 includes means, such as the group-basedclient module 310, communications module 308, input/output module 306,processor 302 and/or the like, or a combination thereof, configured toreceive centralized channel data from a group-based communicationsystem. In at least some embodiments, the centralized channel dataincludes at least a group-based communication channel metadata set foreach group-based communication channel in a manageable group-basedcommunication channel set for an authenticated user account. In thisregard, the authenticated user account may be associated with the clientdevice for example during an authenticated session. It should beappreciated that the manageable group-based communication channel setfor the authenticated user account may be identified by the group-basedcommunication system, for example using one or more queries based on theauthenticated user account and/or a corresponding authenticated useraccount identifier. In some embodiments, the centralized channel data isreceived in response to a centralized channel management request, forexample transmitted at an earlier step, for example block 1502.

At block 1506, the apparatus 300 includes means, such as the group-basedclient module 310, communications module 308, input/output module 306,processor 302 and/or the like, or a combination thereof, configured toprocess the group-based communication channel metadata set. In someembodiments, the group-based communication channel metadata set may beprocessed for performing one or more determinations, such as whether torevoke permission data for accessing one of the manageable group-basedcommunication channels to one or more organizations, workspaces,authenticated user accounts, and/or the like, and/or whether to grantpermission data for accessing one of the manageable group-basedcommunication channels to one or more organizations, workspaces,authenticated user accounts, and/or the like. Alternatively oradditionally, the apparatus 300 may process the group-basedcommunication channel metadata set for purposes of rendering one or moreinterfaces, for example as described herein with respect to block 1508.

At optional block 1508, the apparatus 300 includes means, such as thegroup-based client module 310, communications module 308, input/outputmodule 306, processor 302 and/or the like, or a combination thereof,configured to cause rendering of a centralized channel managementdashboard based on at least the centralized channel data. In at leastsome embodiments, the centralized channel management dashboard includesthe group-based communication channel metadata set, and/or at least aportion thereof. In this regard, as described herein, the centralizedchannel management dashboard may be rendered based at least on thecentralized channel data. Additionally or alternatively, in someembodiments, the centralized channel management dashboard furtherincludes information derived based on data from the group-basedcommunication channel metadata set and/or other information of thecentralized channel data. In some such embodiments, the centralizedchannel management dashboard may be processed and/or analyzed to enablea system and/or user to perform one or more determinations regardingmanagement of a manageable group-based communication channel. In someembodiments, as described herein, in some embodiments the centralizedchannel management dashboard further includes one or more interfaceelements for searching for data within the centralized channelmanagement dashboard, filtering data rendered to the centralized channelmanagement dashboard, and/or the like.

Additionally or alternatively still, in at least some embodiments, thechannel management dashboard includes one or more interface elementsconfigured to enable initiation of one or more management actions viathe group-based communication system. For example, in at least some suchembodiments, the centralized channel management dashboard furtherincludes at least one channel management action interface elementassociated with at least one group-based communication channel of themanageable group-based communication channel set. Alternative oradditionally in some embodiments, a channel management action interfaceelement is associated with a plurality of group-based communicationchannels of the manageable group-based communication channel set. In yetsome other embodiments, the centralized channel management dashboardincludes a plurality of channel management action interface elementsassociated with each manageable group-based communication channel, or aplurality of manageable group-based communication channels. For example,a first channel management action interface element may be configured toinitiate a channel sharing action, a second channel management interfaceelement may be configured to initiate an action for granting and/orrevoking permission data for managing the group-based communicationchannel, and/or the like.

At optional block 1510, the apparatus 300 includes means, such as thegroup-based client module 310, communications module 308, input/outputmodule 306, processor 302 and/or the like, or a combination thereof,configured to transmit a centralized channel management request to agroup-based communication system. In some embodiments, the centralizedchannel management request is associated with an authenticated useraccount identifier corresponding to the authenticated user account. Inthis regard, the authenticated user account identifier may be used tovalidate that the user is properly permissioned for managing one or moregroup-based communication channel(s) identified by data in and/orassociated with the centralized channel management request. For example,in some embodiments, the centralized channel management request includesone or more group-based communication channel identifiers for thechannel(s) to be managed. The channel identifiers may be automaticallydetermined, for example by the apparatus 200, in response to one or moreuser interactions (e.g., with rendered channel management interfaceelement(s)) and/or based at least on one or more determinations (e.g.,identifying channel(s) to be managed).

The centralized management request may represent any number of possibleactions for managing one or more group-based communication channels. Forexample, in some embodiments, the channel management request mayrepresent a user request to initiate a channel archive action (e.g., forarchiving group-based communication messages of at least one group-basedcommunication channel), a channel rename action (e.g., to update namedata associated with at least one group-based communication channel), achannel share action (e.g., to share and/or revoke sharing of at leastone group-based communication channel), and/or a channel delete action(e.g., to mark for deletion, and/or permanently delete, and/or otherwisemake accessible at least one group-based communication channel). Itshould be appreciated that, in some embodiments, a centralized channelmanagement request may be configured to include specific data indicatingthe request is associated with a particular action to be performed. Inone such example context, a transmission may include, or otherwise beconfigured based on, an action identifier that uniquely identifies themanagement action to be performed for the one or more group-basedcommunication channels.

CONCLUSION

Although an example processing system has been described above,implementations of the subject matter and the functional operationsdescribed herein can be implemented in other types of digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them.

Embodiments of the subject matter and the operations described hereincan be implemented in digital electronic circuitry, or in computersoftware, firmware, or hardware, including the structures disclosed inthis specification and their structural equivalents, or in combinationsof one or more of them. Embodiments of the subject matter describedherein can be implemented as one or more computer programs, i.e., one ormore modules of computer program instructions, encoded on computerstorage medium for execution by, or to control the operation of,information/data processing apparatus. Alternatively, or in addition,the program instructions can be encoded on an artificially-generatedpropagated signal, e.g., a machine-generated electrical, optical, orelectromagnetic signal, which is generated to encode information/datafor transmission to suitable receiver apparatus for execution by aninformation/data processing apparatus. A computer storage medium can be,or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially-generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (e.g., multiple CDs, disks, orother storage devices).

The operations described herein can be implemented as operationsperformed by an information/data processing apparatus oninformation/data stored on one or more computer-readable storage devicesor received from other sources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, e.g., a FPGA or an ASIC. The apparatuscan also include, in addition to hardware, code that creates anexecution environment for the computer program in question, e.g., codethat constitutes processor firmware, a protocol stack, a repositorymanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor information/data (e.g., one or more scripts stored in a markuplanguage document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub-programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described herein can be performed by oneor more programmable processors executing one or more computer programsto perform actions by operating on input information/data and generatingoutput. Processors suitable for the execution of a computer programinclude, by way of example, both general and special purposemicroprocessors, and any one or more processors of any kind of digitalcomputer. Generally, a processor will receive instructions andinformation/data from a read-only memory or a random access memory orboth. The essential elements of a computer are a processor forperforming actions in accordance with instructions and one or morememory devices for storing instructions and data. Generally, a computerwill also include, or be operatively coupled to receive information/datafrom or transfer information/data to, or both, one or more mass storagedevices for storing data, e.g., magnetic, magneto-optical disks, oroptical disks. However, a computer need not have such devices. Devicessuitable for storing computer program instructions and information/datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described herein can be implemented on a computer having adisplay device, e.g., a CRT (cathode ray tube) or LCD (liquid crystaldisplay) monitor, for displaying information/data to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described herein can be implemented ina computing system that includes a back-end component, e.g., as aninformation/data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a web browserthrough which a user can interact with an implementation of the subjectmatter described herein, or any combination of one or more suchback-end, middleware, or front-end components. The components of thesystem can be interconnected by any form or medium of digitalinformation/data communication, e.g., a communication network. Examplesof communication networks include a local area network (“LAN”) and awide area network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., an HTML page) toa client device (e.g., for purposes of displaying information/data toand receiving user input from a user interacting with the clientdevice). Information/data generated at the client device (e.g., a resultof the user interaction) can be received from the client device at theserver.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anydisclosures or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular disclosures.Certain features that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

What is claimed is:
 1. A method, implemented by one or more computingdevices of a group-based communication system, comprising: causingpresentation of a channel management interface, of the group-basedcommunication system, via a client of a user associated with a firstorganization, wherein the channel management interface includes aplurality of communication channels associated with the firstorganization, wherein at least a first communication channel of theplurality of communication channels is associated with the firstorganization and a second organization, and wherein at least a secondcommunication channel of the plurality of communication channels isassociated with the first organization and a third organization;receiving, via the channel management interface, a request to initiate achannel management action associated with at least one of the firstcommunication channel or the second communication channel; and inresponse to receiving the request to initiate the channel managementaction, updating data associated with at least one of the firstcommunication channel or the second communication channel.
 2. The methodof claim 1, wherein the channel management action is associated withmodifying user access to at least one of the first communication channelor the second communication channel.
 3. The method of claim 1, whereinthe channel management action is associated with indicating a role of anauthorized user for at least one of approving or rejecting requestsassociated with at least one of the first communication channel or thesecond communication channel.
 4. The method of claim 3, wherein the rolecomprises at least one of an organization primary owner of the firstorganization or an administrator of the first organization.
 5. Themethod of claim 3, wherein the channel management action is associatedwith an indication of which users are permitted to invite other users toat least one of the first communication channel or the secondcommunication channel.
 6. The method of claim 1, further comprising inresponse to receiving the request to initiate the channel managementaction for at least one of the first communication channel or the secondcommunication channel, causing presentation of a channel accesspermissioning interface.
 7. The method of claim 1, further comprising:receiving, via the channel management interface, a request to access achannel information associated with the first communication channel; andin response to receiving the request to access the channel informationassociated with the first communication channel, causing presentation ofa channel information interface via the client, wherein the channelinformation interface indicates that the first organization and thesecond organization have access to the first communication channel. 8.The method of claim 1, further comprising: receiving, via the channelmanagement interface, a request to access a channel informationassociated with the first communication channel; and in response toreceiving the request to access the channel information associated withthe first communication channel, causing presentation of a channelinformation interface via the client, wherein the channel informationinterface includes a notification element indicating that the firstcommunication channel is associated with the second organization.
 9. Themethod of claim 1, wherein the plurality of communication channels isassociated with a third communication channel associated with only thefirst organization, further comprising: receiving, via the channelmanagement interface, a request to update a channel share status of thethird communication channel to enable the third communication channel tobe shared with at least one other organization, than the firstorganization; and in response to receiving the request to update thechannel share status of the third communication channel, updating thechannel share status of the third communication channel.
 10. The methodof claim 1, wherein the plurality of communication channels includes oneor more of: a single-user direct communication channel; a multi-userdirect communication channel; a public communication channel; a privatecommunication channel; or an external resource communication channel.11. A system comprising: one or more processors; and one or morenon-transitory computer-readable media storing instructions that, whenexecuted by the one or more processors, cause the system to performoperations comprising: causing presentation of a channel managementinterface, of a group-based communication system, via a client of a userassociated with a first organization, wherein the channel managementinterface includes a plurality of communication channels associated withthe first organization, wherein at least a first communication channelof the plurality of communication channels is associated with the firstorganization and a second organization, and wherein at least a secondcommunication channel of the plurality of communication channels isassociated with the first organization and a third organization;receiving, via the channel management interface, a request to initiate achannel management action associated with at least one of the firstcommunication channel or the second communication channel; and inresponse to receiving the request to initiate the channel managementaction, updating data associated with at least one of the firstcommunication channel or the second communication channel.
 12. Thesystem of claim 11, wherein the channel management action is associatedwith at least one of: modifying user access to at least one of the firstcommunication channel or the second communication channel; indicating arole of an authorized user for at least one of approving or rejectingrequests associated with at least one of the first communication channelor the second communication channel; or an indication of which users arepermitted to invite other users to at least one of the firstcommunication channel or the second communication channel.
 13. Thesystem of claim 12, wherein the role comprises at least one of anorganization primary owner of the first organization or an administratorof the first organization.
 14. The system of claim 11, the operationsfurther comprising in response to receiving the request to initiate thechannel management action for at least one of the first communicationchannel or the second communication channel, causing presentation of achannel access permissioning interface.
 15. The system of claim 11, theoperations further comprising: receiving, via the channel managementinterface, a request to access a channel information associated with thefirst communication channel; and in response to receiving the request toaccess the channel information associated with the first communicationchannel, causing presentation of a channel information interface via theclient, wherein the channel information interface includes at least oneof: an indication that the first organization and the secondorganization have access to the first communication channel; or anotification element indicating that the first communication channel isassociated with the second organization.
 16. The system of claim 11,wherein the plurality of communication channels is associated with athird communication channel associated with only the first organization,the operations further comprising: receiving, via the channel managementinterface, a request to update a channel share status of the thirdcommunication channel to enable the third communication channel to beshared with at least one other organization, than the firstorganization; and in response to receiving the request to update thechannel share status of the third communication channel, updating thechannel share status of the third communication channel.
 17. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by one or more processors, cause the one or more processors toperform operations comprising: causing presentation of a channelmanagement interface, of a group-based communication system, via aclient of a user associated with a first organization, wherein thechannel management interface includes a plurality of communicationchannels associated with the first organization, wherein at least afirst communication channel of the plurality of communication channelsis associated with the first organization and a second organization, andwherein at least a second communication channel of the plurality ofcommunication channels is associated with the first organization and athird organization; receiving, via the channel management interface, arequest to initiate a channel management action associated with at leastone of the first communication channel or the second communicationchannel; and in response to receiving the request to initiate thechannel management action, updating data associated with at least one ofthe first communication channel or the second communication channel. 18.The one or more non-transitory computer-readable media of claim 17,wherein the channel management action is associated with at least oneof: modifying user access to at least one of the first communicationchannel or the second communication channel; indicating a role of anauthorized user for at least one of approving or rejecting requestsassociated with at least one of the first communication channel or thesecond communication channel; or an indication of which users arepermitted to invite other users to at least one of the firstcommunication channel or the second communication channel.
 19. The oneor more non-transitory computer-readable media of claim 17, theoperations further comprising in response to receiving the request toinitiate the channel management action for at least one of the firstcommunication channel or the second communication channel, causingpresentation of a channel access permissioning interface.
 20. The one ormore non-transitory computer-readable media of claim 17, the operationsfurther comprising: receiving, via the channel management interface, arequest to access a channel information associated with the firstcommunication channel; and in response to receiving the request toaccess the channel information associated with the first communicationchannel, causing presentation of a channel information interface via aclient, wherein the channel information interface includes at least oneof: an indication that the first organization and the secondorganization have access to the first communication channel; or anotification element indicating that the first communication channel isassociated with the second organization.